Repository navigation
Commit 45d2046
ci(stlc): back-sync pushes staging main as the automation identity
Staging main is getting a pull-request rule whose only bypass is the
automation's repository role. The back-sync job pushed with GITHUB_TOKEN,
which cannot be a bypass actor (GitHub Actions is not an org-owned app), so
push with PRODUCTION_REPO_TOKEN (the service account) instead. Token pushes
also trigger seal-dispatch, so the config repo re-seals immediately after a
back-sync rather than at the next scheduled run.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017oDfpQ4KpmpTzYm2fZ9eaL1 parent 5bf88f0 commit 45d2046
1 file changed
Lines changed: 13 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
76 | 76 | | |
77 | 77 | | |
78 | 78 | | |
| 79 | + | |
| 80 | + | |
79 | 81 | | |
80 | 82 | | |
81 | 83 | | |
82 | 84 | | |
83 | 85 | | |
84 | 86 | | |
85 | 87 | | |
86 | | - | |
| 88 | + | |
| 89 | + | |
| 90 | + | |
| 91 | + | |
| 92 | + | |
| 93 | + | |
| 94 | + | |
| 95 | + | |
| 96 | + | |
| 97 | + | |
| 98 | + | |
87 | 99 | | |
88 | 100 | | |
89 | 101 | | |
| |||
0 commit comments