-
Notifications
You must be signed in to change notification settings - Fork 43
keeping ecmascript-modules up to date #197
Comments
If the worry is the process/publicity of the event, we could set up a bot the opens/updates a merge PR regularly (constantly?), then the merge can be resolved publicly on GitHub and pulled in when desirable (still daily?). It'd provide a well-known public audit log of updates performed. |
I don't think it can be a PR, as the changes in question are amendments to existing commits, not new commits. GitHub PRs would just say that's a conflict right? |
It's definitely possible to open a merge PR. Here's an example: nodejs/ecmascript-modules#10 |
@targos but wouldn't conflicts with our branch have to be resolved as changes to the commits from upstream, not our commits? |
I guess they would have to be resolved as part of the merge commits? |
You can resolve (some) merge conflicts in the github webui now. |
Merge commits will make later attempts to land things in node core more difficult; imo the fork should stay consistently rebased on top of core, not littered with merge commits into it. |
We have setup a daily CI job that automatically updates the In case of failure, it can send an email to a list of individuals. I put @MylesBorins and my address. Anyone else would like to be notified? |
Seems like we have this under control now... closing |
our repo needs to be kept up to date with nodejs/node. currently this happens by me rebasing roughly once per day and manually sorting out all the conflicts so we keep our changes. @jdalton has expressed discomfort that this process isn't properly documented.
what should we do moving forward?
The text was updated successfully, but these errors were encountered: