docs(changelog): Docker PR build entry — CONTRIBUTING and PR template list the check - #177
Merged
Merged
Conversation
… list the check #174 took its CHANGELOG entry out to merge main in, and auto-merge squash-merged it before the entry came back, so the entry lands here, with the timings of #174's two runs added: the slim image took 50 to 63 seconds and the office image 76 to 88, and both finished before lint-and-test. #175, merged in the same window, gave CONTRIBUTING.md a "CI gates" section and the pull request template a list of the checks that do not block a merge; both now name the Docker image smoke tests as well. Full suite 1449 green (72 skipped on Windows); ruff clean; docs only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ommits Every PR adds its CHANGELOG entry at the same place, so each merge to main conflicts with every open PR. Taking this PR's entry out lets GitHub merge main in cleanly; the next commit puts it back on top. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
MrChengLen
enabled auto-merge (squash)
September 29, 2026 07:59
MrChengLen
disabled auto-merge
September 29, 2026 08:06
…ommits main moved on (#178, #179, #180 and #170) and adds entries at the top of CHANGELOG.md, so GitHub's update-branch refuses. A merge commit cannot be signed from this machine, so the entry leaves for the merge of main and comes back in the commit after it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…what #170 made stale Puts back the entry taken out for the merge of main, on top of the merged [Unreleased] section, without two sentences #170 made stale: docker.yml now builds without a layer cache, so the PR builds no longer read one that main keeps writing, and the timings measured with that cache no longer describe a run. Full suite 1481 green (72 skipped on Windows) on the merged tree; docs only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ommits Every PR adds its CHANGELOG entry at the same place, so each merge to main conflicts with every open PR. Taking this PR's entry out lets GitHub merge main in cleanly; the next commit puts it back on top. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docs-only follow-up to #174 (Docker PR build + deploy condition, already on
mainas 2d14398):maininto the branch, and auto-merge squash-merged the PR before it came back. Added: the timings of ci(docker): build and smoke-test both images on every pull request — no push #174's two runs (slim image 50–63 s, office image 76–88 s; both finished beforelint-and-test).smoke-test (base)/smoke-test (office).Test plan
mainsucceeded, and Notify Ops Repo ran itsnotifyjob (not skipped) withHTTP 204.🤖 Generated with Claude Code