Skip to content

Conversation

stephenfin
Copy link
Contributor

@stephenfin stephenfin commented Jun 19, 2025

@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

Coverage Status

coverage: 63.81%. remained the same
when pulling 23eae2c on shiftstack:merge-queues
into 7c53a81 on gophercloud:main.

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.

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.

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 6 times, most recently from 3403e4c to b1f9e44 Compare August 12, 2025 14:01
@stephenfin stephenfin marked this pull request as draft August 12, 2025 14:10
@stephenfin
Copy link
Contributor Author

stephenfin commented Aug 12, 2025

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

Or not. I've reworked this PR to take learnings from that one.

@stephenfin stephenfin force-pushed the merge-queues branch 3 times, most recently from ff190bf to f3280dd Compare August 13, 2025 09:57
To allow us to retrieve the list of changed files in the PR and compare
them against a whitelist. This filtering only happens for non-scheduled
jobs. For scheduled jobs, we should always run.

Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
@stephenfin stephenfin force-pushed the merge-queues branch 4 times, most recently from c747b95 to 19f97e3 Compare September 1, 2025 16:44
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>
@stephenfin stephenfin marked this pull request as ready for review September 5, 2025 14:21
@stephenfin
Copy link
Contributor Author

stephenfin commented Sep 5, 2025

@kayrus @mandre I think this is ready to go now. Once we merge this, we can make all but the currently failing job required and turn on merge queues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

Successfully merging this pull request may close these issues.

3 participants