Skip to content

ci: skip the build in the merge queue for changes that don't affect the images - #7696

Merged
viceice merged 1 commit into
mainfrom
viceice/ci/skip-build-merge-queue
Oct 9, 2026
Merged

viceice merged 1 commit into
mainfrom
viceice/ci/skip-build-merge-queue

Conversation

@viceice

@viceice viceice commented Oct 9, 2026

Copy link
Copy Markdown
Member

Changes

Runs the check for changes that don't need the build in the merge queue too, diffing the group against its base, so a group that only changes docs, the dev container or repo settings skips the docker build and tests there as well. Pushes to main and maint/** still always run everything, as they release.

Context

Please select one of the following:

  • This closes an existing Issue, Closes: #
  • This doesn't close an Issue, but I accept the risk that this PR may be closed if maintainers disagree with its opening or implementation

AI assistance disclosure

Did you use AI tools to create any part of this pull request?

Please select one option and, if yes, briefly describe how AI was used (e.g., code, tests, docs) and which tool(s) you used.

  • No — I did not use AI for this contribution.
  • Yes — minimal assistance (e.g., IDE autocomplete, small code completions, grammar fixes).
  • Yes — substantive assistance (AI-generated non‑trivial portions of code, tests, or documentation).
  • Yes — other (please describe):

Claude Opus 5.5 (Claude Code) wrote the workflow change and checked it with jactionlint.

Use of AI in replying to PR comments

Who answers review comments:

  • @viceice will read and reply directly. Name the account.
  • An agent will draft replies and @username will read them before they are posted. Name the account.
  • An agent will draft replies and reply autonomously. This is heavily discouraged, and we prefer that there are humans in the loop
  • Nobody has explicitly committed to replying.

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified tests

🤖 Generated with Claude Code

…he images

Co-Authored-By: Claude Opus 5.5 <michael.kriese+claude-code@mend.io>
@coderabbitai

coderabbitai Bot commented Oct 9, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 27 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Configuration used: Repository: containerbase/coderabbit/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: f9af1fda-27be-4ab4-9fc0-b02c26a75b79

📥 Commits

Reviewing files that changed from the base of the PR and between d1a4211 and 207541a.


📒 Files selected for processing (1)
  • .github/workflows/build.yml


  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Skip merge-queue builds for changes that do not affect images

✨ Enhancement ⚙️ Configuration changes 🕐 10-20 Minutes

Grey Divider

AI Description

• Check merge-queue changes against the group's base, extending the existing pull-request build
 filter.
• Skip Docker builds and tests for qualifying groups; retain full builds for release pushes.
Diagram

graph TD
  PR["Pull request"] --> Compare["Compare base"] --> Gate{"Build needed?"} --> Docker["Docker jobs"]
  Merge["Merge group"] --> Compare
  Gate --> Bats["Bats tests"]
  Push["Release push"] --> Docker
Loading
High-Level Assessment

Reusing the existing changed-file filter is appropriate: it applies one exclusion policy to pull requests and merge groups while leaving release pushes untouched. Separate merge-queue filtering would duplicate that policy.

Files changed (1) +7 / -7

Other (1) +7 / -7
build.ymlApply the build-skip check to merge groups +7/-7

Apply the build-skip check to merge groups

• Runs the existing changed-file check for merge-group events as well as pull requests, using the merge group's base SHA for comparison. Updates the comment to clarify that pushes still run the full build.

.github/workflows/build.yml

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can show, collapse, or hide each part of a finding: code, evidence, and all

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

@viceice
viceice enabled auto-merge October 9, 2026 09:49
@viceice
viceice added this pull request to the merge queue Oct 9, 2026
Merged via the queue into main with commit 52b19c3 Oct 9, 2026
61 checks passed
@viceice
viceice deleted the viceice/ci/skip-build-merge-queue branch October 9, 2026 10:44
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.

1 participant