stop drift checks on prs (#22)
Reviewed-on: #22 Co-authored-by: vickydotbat <vickydotbat@tutamail.com> Co-committed-by: vickydotbat <vickydotbat@tutamail.com>
This commit was merged in pull request #22.
This commit is contained in:
@@ -2,6 +2,9 @@
|
||||
# main. Maintenance automation (not artifact publishing), so it is allowed on a
|
||||
# main push under the D7 trigger standard. Requires BOT_TOKEN: the gitea-bot
|
||||
# org token (content+PR write to the consumer repos; never committed).
|
||||
#
|
||||
# Consumer drift checks run only after their sync PRs merge to main. They must
|
||||
# not run on the sync PR itself, which can create recursive cross-repo checks.
|
||||
name: sync-wrappers
|
||||
|
||||
on:
|
||||
|
||||
@@ -91,6 +91,8 @@ publish event is a `v*` tag (see `sow-docs/runbooks/ci-trigger-standard.md`).
|
||||
- `publish-image.yml` — manual `workflow_dispatch` break-glass republish.
|
||||
- `sync-wrappers.yml` — on a `main` push that touches `wrappers/`, auto-PR the
|
||||
canonical wrappers to the consumer repos in `wrappers/consumers.txt`.
|
||||
Consumer drift checks run after those PRs merge to `main`, not on the PRs
|
||||
themselves, to avoid recursive cross-repo checks.
|
||||
|
||||
## Consumers
|
||||
|
||||
|
||||
Reference in New Issue
Block a user