Remove the paths-ignore option from all build workflows #638
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
The idea here was probably to avoid wasting CI time... but it prevents minor changes, like #637, from being merged because all build workflows are required checks. GitHub's branch protection feature is clearly half-baked. Luckily minor changes like these virtually never happen, so for the time being it shouldn't be a big problem to remove this setting.
rdw-software
added a commit
that referenced
this pull request
Jan 10, 2025
Follow-up to #638. This is still blocking and it doesn't seem very useful. Perhaps there's a more reliable way of filtering irrelevant changes? (I should look into that eventually)
rdw-software
added a commit
that referenced
this pull request
Jan 10, 2025
Follow-up to #638. This is still blocking and it doesn't seem very useful. Perhaps there's a more reliable way?
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.
The idea here was probably to avoid wasting CI time... but it prevents minor changes, like #637, from being merged because all build workflows are required checks. GitHub's branch protection feature is clearly half-baked. Luckily minor changes like these virtually never happen, so for the time being it shouldn't be a big problem to remove this setting.
Edit: I'd also prefer for the CI to be less wasteful by means of being faster, but that's a future concern.