Repository navigation
Scope Update Readme to pushes on main - #19
Merged
matt-edmondson merged 1 commit intoSep 16, 2026
Merged
Conversation
`on: push:` with no filter fires on every branch and every tag, and both are wrong for a workflow that regenerates the organization profile README. On a tag, actions/checkout leaves a detached HEAD, so the commit step's bare `git push` has no upstream and the run fails. That matters now rather than in the abstract: the shared CI callers reference a moving `release` tag, so every promotion would have produced a failing run in this repository. On a feature branch it regenerates a file that only means anything on main and commits it to that branch. Three pull requests in a row picked up a bot README commit they had no reason to carry, and on #18 main and the branch regenerated different snapshots of the same table and conflicted -- a merge conflict in a generated file, on a pull request that never touched it. The schedule and manual triggers are unchanged; main still regenerates on every push, which is the only place the profile README is read from. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014RABe2NufFc9hwm94iB3Rf
matt-edmondson
deleted the
claude/dependabot-ci-workflow-rollout-fbrhdn
branch
September 16, 2026 03:50
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
2 participants
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.
What
update-readme.yml:on: push:→on: push: branches: [main]. Schedule and manual triggers unchanged.Why
An unfiltered
push:fires on every branch and every tag, and both are wrong for a workflow that regenerates the organization profile README.On a tag —
actions/checkoutleaves a detached HEAD, so the commit step's baregit pushhas no upstream to push to and the run fails. This is a blocker rather than a hypothetical: the shared CI callers reference a movingreleasetag, so every promotion would produce a failing run in this repository. Thereleasetag cannot be created until this merges — a tag pushed today would use the version of this workflow at that commit and still fail.On a feature branch — it regenerates a file that only means anything on
mainand commits it to whatever branch was pushed. That is not theoretical either:[skip ci][bot] Update README.mdcommit they had no reason to carry.mainand the PR branch each regenerated the table from a different snapshot of live org state (Essentials v2.6.1 vs v2.6.2, Extensions passing vs failing) and the two diverged. A generated file conflicted on a pull request that never touched it.mainstill regenerates on every push, which is the only place the profile README is read from, so the profile page is unaffected.Testing
actionlint1.7.7 withshellcheck— no new findings. The two pre-existing SC2086 infos in this file are untouched.The mechanism is the documented behaviour of an unfiltered
push:trigger, and the branch-push half of it is directly evidenced by the bot commits on #16–#18 and the conflict I resolved on #18.🤖 Generated with Claude Code
https://claude.ai/code/session_014RABe2NufFc9hwm94iB3Rf
Generated by Claude Code