Document [skip ci] directive behavior to prevent release workflow suppression #5
+8
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The latest commit on main didn't trigger the release workflow because it contained
[skip ci]in the commit message. This GitHub Actions directive suppresses all workflow execution, including release automation.Changes
README.md: Added warning in Contributing section that
[skip ci],[ci skip], and similar directives prevent release workflows from running. Specified these should only be used on feature branches.release.yml: Added inline comments documenting that the workflow won't run when skip directives are present in commit messages.
Context
The workflow trigger configuration was correct—the issue was improper use of skip directives on main branch commits.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.