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

Testing of Github Merge Queue #5102

Closed
non-fungible-nelson opened this issue Feb 16, 2023 · 10 comments
Closed

Testing of Github Merge Queue #5102

non-fungible-nelson opened this issue Feb 16, 2023 · 10 comments
Assignees
Labels
dev experience The build system, things that enable easier development etc. TeamRevenant GH issues worked on by Revenant Team

Comments

@non-fungible-nelson
Copy link
Contributor

https://github.blog/changelog/2023-02-08-pull-request-merge-queue-public-beta/

Testing of merge queue for Github to avoid conflicts going forward.

@non-fungible-nelson non-fungible-nelson added dev experience The build system, things that enable easier development etc. TeamRevenant GH issues worked on by Revenant Team labels Feb 16, 2023
@macfarla
Copy link
Contributor

I tried merge queue in a test repo - works as expected.

  • PR A with no conflicts merged without trouble
  • PR B with conflict resulting from PR A was removed from the merge queue
  • PR C with conflict resulting from PR A was able to be added to the merge queue - it's still sitting there waiting for the conflict to be resolved
  • PR D reverting an earlier PR was merged without trouble
    I still have some unmerged PRs sitting there if anyone else wants to play with it

@macfarla
Copy link
Contributor

Squash commits?
I set the settings in the test repo to match besu - ie allow squash merging. The "add to merge queue" button doesn't show any options around squash commits, and the PR I created with multiple commits did not get squashed. (This commit and the two before it are from the same PR https://github.com/daisy-row/vigilant-octo-umbrella/commit/78576553486c62e44eb17837e870d537ab34d5c6) Not sure if there's something else in Besu repo settings that would make this behave differently.

@macfarla
Copy link
Contributor

macfarla commented Feb 20, 2023

Looks like you can choose options when setting up merge queue. Have asked Ry for admin access to the test repo. https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue#managing-a-merge-queue

@macfarla
Copy link
Contributor

macfarla commented Feb 20, 2023

Now we have merge queue + squash commits - see commits from Feb 21
https://github.com/daisy-row/vigilant-octo-umbrella/commits/main

@macfarla
Copy link
Contributor

added DCO as a required check

@macfarla
Copy link
Contributor

@macfarla
Copy link
Contributor

DCO strikes again - the DCO that we use https://github.com/tim-actions/dco does not support merge_group event trigger (neither does it support merge events which is why we have this open issue #4837) - we can investigate other dco options (write our own? dcoapp doesn't support merge queue yet either dcoapp/app#199). But DCO has to be a required check at that point, there isn't a separate set of checks for the merge queue.

So for now have turned off merge queue. Back to status quo.

@macfarla
Copy link
Contributor

@macfarla
Copy link
Contributor

#5207

@macfarla macfarla reopened this Mar 13, 2023
@macfarla
Copy link
Contributor

Merge queue update - I think we have a solution!

Added a separate "dco" check that is triggered by the merge_group event but doesn't check anything #5207 (existing dco check runs on pull_request event as before) - and merge queue is happily running it eg this PR #5209 is merging via the merge queue - and here is the dco job - https://github.com/hyperledger/besu/actions/runs/4402919772/jobs/7710635563

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev experience The build system, things that enable easier development etc. TeamRevenant GH issues worked on by Revenant Team
Projects
None yet
Development

No branches or pull requests

2 participants