Prevent python3-ntp and libhashkit workflows from running on every push#258
Merged
aidangarske merged 1 commit intoAug 12, 2025
Merged
Conversation
Member
|
Whats the reason for this do they take longer than the other runs now? |
Contributor
Author
Seems like something left over from development. This change aligns these yamls with the rest of them. |
aidangarske
approved these changes
Aug 12, 2025
aidangarske
left a comment
aidangarske
left a comment
Member
There was a problem hiding this comment.
So the changes are not to prevent them from running but to allow them to run on every push. Correct?
Contributor
Author
No, it's the other way around. It will now only run for pushes to master, main and release branches. Also, a push to any branch with a PR will trigger it. |
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
2 participants
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.
No description provided.