ci: push dropdown updates with ACCESS_TOKEN_ARMBIANWORKER (workflow scope) - #45
Conversation
…cope) The "Update board/maintainer dropdowns" job edits build-standard-support.yml (a workflow file) and pushes it. GitHub rejects PAT pushes that touch .github/workflows/* without the `workflow` scope, which secrets.ACCESS_TOKEN lacks: ! [remote rejected] ... refusing to allow a Personal Access Token to create or update workflow `.github/workflows/build-standard-support.yml` without `workflow` scope Use the ACCESS_TOKEN_ARMBIANWORKER token (which carries the workflow scope) for the create-pull-request step instead. Signed-off-by: Igor Pecovnik <igor@armbian.com>
|
Warning Review limit reached
Next review available in: 55 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Why
The Update board/maintainer dropdowns job (run 30981939716) fails at the push:
The job regenerates the
workflow_dispatchdropdowns, which live insidebuild-standard-support.yml(a workflow file). GitHub blocks any PAT push touching.github/workflows/*unless the token has theworkflowscope — whichsecrets.ACCESS_TOKENdoesn't.Change
create-pull-requesttoken:→secrets.ACCESS_TOKEN_ARMBIANWORKER(carries theworkflowscope).Only usage of the token in this workflow; nothing else changes.
Follow-up to #44 (which cleared the Node 20 deprecation on the same step).