By default, when a workflow uses GITHUB_TOKEN to create a commit or open a pull request, what happens regarding additional workflow runs?
Select an answer to reveal the explanation.
Short Explanation and Infographic
GITHUB_TOKEN-generated events intentionally do not trigger new workflows. That avoids infinite CI loops when a bot commit would otherwise re-fire the same pipeline.
Full explanation below image
Full Explanation
If actions using GITHUB_TOKEN push commits, create tags, or open PRs, those events will not trigger further workflow runs that listen for push or pull_request. This is a deliberate guard against recursive workflows. To trigger workflows from automation, use a personal access token, GitHub App installation token, or other non-GITHUB_TOKEN credential with care and least privilege. The wrong options overstate elevated permissions, repository disablement, or schedule-only suppression. Understanding this behavior is important when designing release automation that must kick off downstream workflows — you may need a carefully scoped App token, not GITHUB_TOKEN, and you should document why that exception exists.