Repository navigation
Install the tag-on-merge caller — canary stage 1 of opencharly/.github#204 #6
Description
This repo has no .github/workflows directory at all, so its PRs merge and never get a merge-time CalVer tag. Measured: the newest tags are v2026.266.1833 / v2026.266.1724 (day 266, eleven days before PR #5 merged 2026-10-15T07:42:56Z as 79feb02), and charly/pr-validator passed on that head while no tag was written.
This is canary stage 1 of opencharly/.github#204, authorised by the operator. A fresh org-wide sweep of 457 non-archived repos found 29 lacking a tag-on-merge caller; this repo is the worst case because the install path starts from nothing.
THE CHANGE: add .github/workflows/tag-on-merge.yml, byte-identical to the dispatcher carried by repos whose tags work (plugin-box, layer-charly-build, plugin-deploy-pod). The file is copied rather than retyped and the copy is proven by hash: written d657e2c1ed7b7343, plugin-box d657e2c1ed7b7343, layer-charly-build d657e2c1ed7b7343.
No backfill of the missing v2026.288.0742 tag is proposed here: tags are add-only and the tag-on-merge sweep is idempotent over the last 24h, so the merged PR self-heals once the caller exists. That backfill decision belongs to the operator and is deliberately not taken in this issue.
Agent: lead
Assisted-by: DeepSeek Harness ollama-cloud/deepseek-v4.1-flash (analysed on a live system)
Activity
aitrawog commentedon Oct 15, 2026
CLAIM — taking this one, canary stage 1 of opencharly/.github#204, authorised by the operator on the worst-case repo (no .github/workflows at all).
Agent: lead
Assisted-by: DeepSeek Harness ollama-cloud/deepseek-v4.1-flash (analysed on a live system)
aitrawog commentedon Oct 15, 2026
RESOLVED — #7 merged 2026-10-15T10:48:04Z as caa9e87, and the caller is installed. Closing by hand, since a Closes #N line does not close an issue by itself.
WHAT LANDED: .github/workflows/tag-on-merge.yml, byte-identical to the dispatcher carried by plugin-box, layer-charly-build and plugin-deploy-pod (sha256 d657e2c1ed7b7343 across all four).
WHAT THE CANARY FOUND, recorded here because it will bite every other repo the rollout touches: installing the caller does NOT tag the merge that installs it. Both of the dispatcher's triggers miss that first merge by construction — push:[main] cannot observe auto-merge squashes (documented in the file's own header), and workflow_run needs a charly/pr-validator completion that comes AFTER the file exists on main, which the installing merge itself prevents. Tagging here resumed by operator-authorised add-only backfill: v2026.288.0742 on 79feb02 (PR #5) and v2026.288.1048 on caa9e87 (PR #7), both verified present and pointing at their merge commits, with the two pre-existing day-266 tags untouched.
STILL OPEN, NOT THIS ISSUE: the repo has no CHANGELOG/ entries — those are written by the tag-on-merge sweep, which has not yet run here and should do so on the next charly/pr-validator completion in this repo. Tracked on opencharly/.github#204.
Agent: lead
Assisted-by: DeepSeek Harness ollama-cloud/deepseek-v4.1-flash (analysed on a live system)