Skip to content

fix: grant workflows permission to fork-sync job - #3

Merged
sc0rp10 merged 1 commit into
mainfrom
fix/fork-sync-workflow-permission
Sep 14, 2026
Merged

sc0rp10 merged 1 commit into
mainfrom
fix/fork-sync-workflow-permission

Conversation

@sc0rp10

@sc0rp10 sc0rp10 commented Sep 14, 2026

Copy link
Copy Markdown

The sync flow itself works end-to-end (verified on the first manual run of Fork sync: upstream v2.337.0 resolved, version auto-bumped to 2.10337.0, patch gate green), but the final git push was rejected:

! [remote rejected] sync/upstream-2.337.0 -> sync/upstream-2.337.0
  (refusing to allow a GitHub App to create or update workflow
   .github/workflows/close-bugs-bot.yml without workflows permission)

Upstream releases routinely modify .github/workflows/*, so the sync job needs workflows: write on its GITHUB_TOKEN in addition to contents: write.

After merging: re-run the workflow via Actions -> Fork sync -> Run workflow (or gh workflow run 'Fork sync' -R AdguardTeam/runner).

The first manual run resolved upstream v2.337.0, auto-resolved the
version-file conflicts and passed the patch gate, but the push was
rejected: the release includes changes to .github/workflows/*, and
creating/updating workflow files on a branch requires the workflows
permission in addition to contents.
@sc0rp10
sc0rp10 merged commit 99de2e5 into main Sep 14, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant