Skip to content

docs: warn about GITHUB_TOKEN limitation for status checks#124

Open
ricogu wants to merge 1 commit into
mainfrom
docs-warn-github-token-status-checks
Open

docs: warn about GITHUB_TOKEN limitation for status checks#124
ricogu wants to merge 1 commit into
mainfrom
docs-warn-github-token-status-checks

Conversation

@ricogu

@ricogu ricogu commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Summary

Documents a known GitHub platform limitation: when consumers pass secrets.GITHUB_TOKEN as the token input, commits pushed by this action are made by the github-actions[bot] identity, and GitHub intentionally does not re-trigger other workflow runs on such pushes. This means CI checks, tests, linting, and other status checks will not run on the version-bump commit.

Changes Made

  • action.yml: Expanded token input description to include an inline warning about the GITHUB_TOKEN limitation and guidance to use a PAT or GitHub App token instead.
  • README.md: Added a dedicated GITHUB_TOKEN and Status Checks section under Inputs with a clear warning, explanation, and code example for using a PAT.

Type of Change

  • Documentation update

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • My changes generate no new warnings

When consumers pass secrets.GITHUB_TOKEN, commits pushed by this action
are made by github-actions[bot] and GitHub will not re-trigger other
workflow runs (CI, tests, etc.) on the bump commit.

Document this limitation in action.yml token input description and add
a dedicated section in the README with guidance on using a PAT or
GitHub App token instead.
@ricogu ricogu enabled auto-merge (squash) June 13, 2026 13:27
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