Skip to content
This repository has been archived by the owner on Sep 2, 2023. It is now read-only.

keeping ecmascript-modules up to date #197

Closed
devsnek opened this issue Oct 9, 2018 · 9 comments
Closed

keeping ecmascript-modules up to date #197

devsnek opened this issue Oct 9, 2018 · 9 comments
Labels

Comments

@devsnek
Copy link
Member

devsnek commented Oct 9, 2018

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?

@devsnek devsnek added the meta label Oct 9, 2018
@weswigham
Copy link
Contributor

weswigham commented Oct 10, 2018

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.

@devsnek
Copy link
Member Author

devsnek commented Oct 10, 2018

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?

@targos
Copy link
Member

targos commented Oct 10, 2018

It's definitely possible to open a merge PR. Here's an example: nodejs/ecmascript-modules#10

@devsnek
Copy link
Member Author

devsnek commented Oct 10, 2018

@targos but wouldn't conflicts with our branch have to be resolved as changes to the commits from upstream, not our commits?

@targos
Copy link
Member

targos commented Oct 10, 2018

I guess they would have to be resolved as part of the merge commits?
Maybe we can ask the people involved in HTTP/2 development how they managed updates to their fork?

@weswigham
Copy link
Contributor

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?

You can resolve (some) merge conflicts in the github webui now.

@ljharb
Copy link
Member

ljharb commented Oct 10, 2018

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.

@targos
Copy link
Member

targos commented Nov 24, 2018

We have setup a daily CI job that automatically updates the master and modules-lkgr branches: https://ci.nodejs.org/view/All/job/node-update-ecmascript-modules/

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?

@MylesBorins MylesBorins removed the modules-agenda To be discussed in a meeting label Nov 30, 2018
@MylesBorins
Copy link
Contributor

Seems like we have this under control now... closing

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants