Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync only to the upstream branch and do not cherry-pick #4864

Merged
merged 1 commit into from
Dec 16, 2024
Merged

Conversation

mrobinson
Copy link
Member

Upstream sometimes uses merge commits which make it very difficult to
maintain a cherry-pick based sync workflow. This change modifies the way
syncing works so that it simply does a hard reset of the branch to the
filtered repository. This should be more foolproof, with the downside
that main is no longer up to date with upstream. Instead a new
upstream branch is always up-to-date.

Fixes #4861.

@mrobinson mrobinson requested a review from mukilan December 16, 2024 09:19
if [ $number_of_commits != '0' ]; then
step "Applying $number_of_commits new commits"
git -c user.email="$git_email" -c user.name="$git_name" cherry-pick $hash..filtered-upstream/master
git rev-parse filtered-upstream/master > "$hash_file"
Copy link
Member

@mukilan mukilan Dec 16, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are no longer updating the hash_file, so is https://github.com/servo/webrender/blob/main/.github/sync/UPSTREAM_COMMIT still needed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope. It's not needed at all. I've removed it in the latest version of this branch.

Upstream sometimes uses merge commits which make it very difficult to
maintain a cherry-pick based sync workflow. This change modifies the way
syncing works so that it simply does a hard reset of the branch to the
filtered repository. This should be more foolproof, with the downside
that `main` is no longer up to date with upstream. Instead a new
`upstream` branch is always up-to-date.

Fixes #4861.
@mrobinson mrobinson merged commit c4bd5b4 into main Dec 16, 2024
@mrobinson mrobinson deleted the update-sync branch December 16, 2024 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Sync is failing
2 participants