Skip to content

Add when to use a token section - #1090

Open
legendecas wants to merge 1 commit into
nodejs:mainfrom
legendecas:when-to-use-a-token
Open

Add when to use a token section#1090
legendecas wants to merge 1 commit into
nodejs:mainfrom
legendecas:when-to-use-a-token

Conversation

@legendecas

@legendecas legendecas commented Aug 28, 2026

Copy link
Copy Markdown
Member

GitHub introduced approval-required state for recursive workflow runs: https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/trigger-a-workflow#triggering-a-workflow-from-a-workflow. This could alleviate some cases from using a PAT by manually approve workflow runs for an automated PR, such as release-please.

The approval UI is identical to a first-time-contributor opening a PR.

image

We could decommission some of the tokens on the registry.

@legendecas
legendecas force-pushed the when-to-use-a-token branch from 175563a to 5fa41b2 Compare August 28, 2026 13:36
@legendecas
legendecas force-pushed the when-to-use-a-token branch from 5fa41b2 to 26f7098 Compare August 28, 2026 13:42
@legendecas

legendecas commented Aug 28, 2026

Copy link
Copy Markdown
Member Author

Example PR: nodejs/node-addon-api#1753 created by an automated release-please workflow with the default token, and it can run CI actions by manual approval.

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.

3 participants