workflows/no-channel: run again when base changed#404461
Merged
Mic92 merged 1 commit intoNixOS:masterfrom May 5, 2025
Merged
Conversation
Because of the branches filter, the job would **not** re-run when only the base-branch was changed, thus leaving the contributor with a failed check. With this change, the job should be triggered and then skipped in this case, so the check in the list should be replaced with a skip. Note, this also means that this step will show up in every PR as skipped, even when it was never failed before.
Contributor
|
Successfully created backport PR for |
1 task
Merged
Member
|
Tested in #404443 |
This file contains hidden or 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
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.
Because of the branches filter, the job would not re-run when only the base-branch was changed, thus leaving the contributor with a failed check.
With this change, the job should be triggered again and then skipped in this case, so the check in the list should be replaced with a skip.
Note, this also means that this step will show up in every PR as skipped, even when it was never failed before.
Things done
Add a 👍 reaction to pull requests you find important.