Skip to content

ci: push dropdown updates with ACCESS_TOKEN_ARMBIANWORKER (workflow scope) - #45

Merged
igorpecovnik merged 1 commit into
mainfrom
ci/dropdowns-use-armbianworker-token
Aug 5, 2026
Merged

ci: push dropdown updates with ACCESS_TOKEN_ARMBIANWORKER (workflow scope)#45
igorpecovnik merged 1 commit into
mainfrom
ci/dropdowns-use-armbianworker-token

Conversation

@igorpecovnik

Copy link
Copy Markdown
Member

Why

The Update board/maintainer dropdowns job (run 30981939716) fails at the push:

! [remote rejected] automation/board-maintainer-dropdowns (refusing to allow a
Personal Access Token to create or update workflow
`.github/workflows/build-standard-support.yml` without `workflow` scope)
error: failed to push some refs to 'https://github.com/armbian/ci'

The job regenerates the workflow_dispatch dropdowns, which live inside build-standard-support.yml (a workflow file). GitHub blocks any PAT push touching .github/workflows/* unless the token has the workflow scope — which secrets.ACCESS_TOKEN doesn't.

Change

  • create-pull-request token:secrets.ACCESS_TOKEN_ARMBIANWORKER (carries the workflow scope).

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).

…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>
@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@igorpecovnik, you've reached your PR review limit, so we couldn't start this review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 49f24612-61f6-4214-a01a-14a06da39c79

📥 Commits

Reviewing files that changed from the base of the PR and between ed62951 and 55b8f84.

📒 Files selected for processing (1)
  • .github/workflows/update-workflow-board-lists.yml

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@igorpecovnik
igorpecovnik merged commit 9aa1480 into main Aug 5, 2026
1 check passed
@igorpecovnik
igorpecovnik deleted the ci/dropdowns-use-armbianworker-token branch August 5, 2026 06:41
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