I have done this in the past. I did it the hard way[1], and it took about 30 minutes. The easy way[2] would take a minimum of several hours.
In cases where we are not significantly impacting code and or dependencies, I think it is okay to just do the work commit it and push to master [1] just doing it, repeatedly for each ... got pretty fast by repo number 3 [2] writing a script to do it, testing the script, fixing the script, trying to figure out how to undo all the mistakes from the last time you ran the script PS: If you are absolutely sure you know what you are doing, you could use the coho for-each command coho for-each -r android -r ios -r windows "git checkout -b UpdateTest && git commit --allow-empty -m 'testing coho for-each' && git push origin UpdateTest && git checkout master" @purplecabbage risingj.com On Fri, Dec 7, 2018 at 4:38 PM Jan Piotrowski <piotrow...@gmail.com> wrote: > Hi. > > For several open tasks (e.g. updating `package.json` across many > repos, distributing the GitHub Issue and PR templates, updating the > plugin CI configuration) we will have to change files in many > repositories and then create a PR (which means the changes have to be > applied in a new branch or even fork) on Github to be reviewed and > merged. > > Currently we don't have and I don't know of any proper tooling for this. > We have cordova-coho, but that can "only" check out, update and > commit/push repositories. > > Do you know of any software, tools or libraries that might help here? > If not, can you maybe help to get this implemented in coho? I created > https://github.com/apache/cordova-coho/issues/222 to track this. > > Thanks, > Jan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
