Skip to content

Prepare for merge queues #3437

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.

Sign up for GitHub

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

Jump to bottom
Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Prepare for merge queues #3437

wants to merge 2 commits into from

Conversation

stephenfin
Copy link
Contributor

@stephenfin stephenfin commented Jun 19, 2025 •
edited
Loading

@github-actions github-actions bot added semver:patch No API change backport-v2 This PR will be backported to v2 edit:actions This PR updates GitHub Actions code edit:testinfra This PR updates testing infrastructure code labels Jun 19, 2025
@coveralls
Copy link

coveralls commented Jun 19, 2025 •
edited
Loading

Coverage Status

coverage: 63.73%. remained the same
when pulling f3280dd on shiftstack:merge-queues
into a448b65 on gophercloud:main.

mandre
mandre approved these changes Jun 20, 2025
View reviewed changes
Copy link
Contributor

@mandre mandre left a comment •
edited
Loading

Choose a reason for hiding this comment

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

This commit doesn't enable merge queues, but prepares for enabling merge queues. We'll still have to configure it in the branch protection as explained here.

As I understand it, we also need to start making more jobs required for it to have any meaningful effect.

mandre
mandre requested changes Jun 20, 2025
View reviewed changes
Copy link
Contributor

@mandre mandre left a comment

Choose a reason for hiding this comment

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

Actually, we'll also need to trigger the hold workflow on merge_group events, since this job is required.

@stephenfin stephenfin changed the title Enable merge queues Prepare for merge queues Aug 11, 2025
@stephenfin
Copy link
Contributor Author

This commit doesn't enable merge queues, but prepares for enabling merge queues. We'll still have to configure it in the branch protection as explained here.

Good point. Done.

As I understand it, we also need to start making more jobs required for it to have any meaningful effect.

Yeah, and for that to happen we need to ensure we always "run" all unit test and functional jobs and simply make them no-ops if they don't apply.

@stephenfin stephenfin force-pushed the merge-queues branch 5 times, most recently from fe98f83 to 95fed32 Compare August 12, 2025 11:34
@stephenfin stephenfin marked this pull request as draft August 12, 2025 14:10
@stephenfin
Copy link
Contributor Author

This will be a good deal easier to do once #3490 is landed.

@stephenfin stephenfin force-pushed the merge-queues branch 2 times, most recently from 0e4b7f8 to ff190bf Compare August 12, 2025 16:53
@stephenfin
Always run functional tests
f3280dd 
Inspired by [1].

[1] https://brunoscheufler.com/blog/2022-04-24-required-github-actions-jobs-in-a-monorepo

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mandre mandre mandre requested changes

Requested changes must be addressed to merge this pull request.

Assignees
No one assigned
Labels
backport-v2 This PR will be backported to v2 edit:actions This PR updates GitHub Actions code edit:testinfra This PR updates testing infrastructure code semver:patch No API change
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@stephenfin @coveralls @mandre