From d216d1a53ac809b269bdc1357f5ff77f96c3f642 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 16 Sep 2026 03:48:48 +0000 Subject: [PATCH] Scope Update Readme to pushes on main `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 Claude-Session: https://claude.ai/code/session_014RABe2NufFc9hwm94iB3Rf --- .github/workflows/update-readme.yml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.github/workflows/update-readme.yml b/.github/workflows/update-readme.yml index 1bc8cf5..dc87282 100644 --- a/.github/workflows/update-readme.yml +++ b/.github/workflows/update-readme.yml @@ -2,6 +2,13 @@ name: Update Readme on: push: + # Branch-scoped deliberately. An unfiltered `push:` fires on every branch and every + # tag. On a tag it checks out a detached HEAD, so the commit step's bare `git push` + # has no upstream to push to and the run fails -- which would happen every time the + # `release` tag is moved. On a feature branch it regenerates a file that only matters + # on main and commits it there, which is how the profile README came to conflict + # between main and a pull request branch that never touched it. + branches: [main] schedule: - cron: '0 0 * * *' workflow_dispatch: