From e4e1bf4080d563fe90d4d61eead80019dcf58d29 Mon Sep 17 00:00:00 2001 From: claude-ceo-assistant Date: Thu, 7 May 2026 15:35:22 -0700 Subject: [PATCH] ci(canary): annotate EXPECTED_PERSONA dual-update constraint MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Hostile-self-review weakest-spot #2: if the devops-engineer persona is ever renamed, the canary will go red even if everything else is fine. Add an inline comment pointing the next editor at both files that must update together (auto-sync-main-to-staging.yml's git config + this canary's EXPECTED_PERSONA + the staging branch protection's push_whitelist_usernames). No behaviour change — comment-only. --- .github/workflows/auto-sync-canary.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/workflows/auto-sync-canary.yml b/.github/workflows/auto-sync-canary.yml index f5304761..f6b0437b 100644 --- a/.github/workflows/auto-sync-canary.yml +++ b/.github/workflows/auto-sync-canary.yml @@ -176,6 +176,10 @@ jobs: # repeating the secret reference. GitHub masks the value in # logs automatically. AUTO_SYNC_TOKEN: ${{ secrets.AUTO_SYNC_TOKEN }} + # MUST stay in sync with auto-sync-main-to-staging.yml's + # `git config user.name "devops-engineer"` line. Renaming the + # devops-engineer persona requires updating both files (and + # the staging branch protection's `push_whitelist_usernames`). EXPECTED_PERSONA: devops-engineer GITEA_HOST: git.moleculesai.app REPO_PATH: molecule-ai/molecule-core