Skip to content

feat: default github-token to github.token#9

Merged
anneschuth merged 2 commits into
mainfrom
feat/github-token-default
Feb 2, 2026
Merged

feat: default github-token to github.token#9
anneschuth merged 2 commits into
mainfrom
feat/github-token-default

Conversation

@robbertbos

@robbertbos robbertbos commented Jan 31, 2026

Copy link
Copy Markdown
Member

Description

The github-token input now defaults to ${{ github.token }}, so users no longer need to explicitly pass github-token: ${{ secrets.GITHUB_TOKEN }}.

This follows the same pattern as GitHub's official actions/checkout action.

Before:

comment-on-pr: true
github-token: ${{ secrets.GITHUB_TOKEN }}

After:

comment-on-pr: true

A custom token is only needed for cross-repository operations or when using a PAT.

Note: Users still need to set permissions at workflow level (e.g., pull-requests: write).

Type of Change

  • Bug fix
  • New feature
  • Breaking change (changes to action inputs/outputs)
  • Documentation update

Checklist

  • I have tested these changes locally
  • I have updated the documentation (if applicable)
  • My changes follow the existing code style
  • I have added/updated comments where necessary

Testing

  • Verified syntax matches GitHub's actions/checkout pattern
  • Validated action.yml files are valid YAML

Breaking Changes

None. Fully backwards compatible - existing workflows that explicitly pass github-token will continue to work.

References

The github-token input now defaults to the automatic workflow token,
so users no longer need to explicitly pass github-token: ${{ secrets.GITHUB_TOKEN }}.

This follows the same pattern as GitHub's official actions/checkout action.
A custom token is only needed for cross-repository operations or when using a PAT.

Note: Users still need to set permissions at workflow level (e.g., pull-requests: write).
@anneschuth anneschuth merged commit 9246aa8 into main Feb 2, 2026
7 checks passed
@anneschuth anneschuth deleted the feat/github-token-default branch February 2, 2026 11:48
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.

2 participants