Except doc files from CI runs #128
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Running CI over changing the README is a waste! I just tested this in a personal repo of mine and was delighted that it works. I can't demonstrate that it works in this pull request 'on pull request' considers all files changed in the PR and this change necessarily changes the ci.yml, but I can show where it's worked elsewhere.
|
github/docs#8926 Looks like the recommendation is to separate the required checks into a separate workflow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Running CI over changing the README is a waste! I just tested this in a personal repo of mine and was delighted that it works. I can't demonstrate that it works in this pull request 'on pull request' considers all files changed in the PR and this change necessarily changes the ci.yml, but I can show where it's worked elsewhere.
Note this isn't compatible with the "Require status checks to pass before merging" branch protection setting. I wasn't sure if we used that, but it looks like we do have a number of required checks that this would cause trouble for -- the CI wouldn't run automatically, so docs PRs would be left stuck.