ci: ignore unrelated workflows, so we don't run extraneous builds#358
Merged
Conversation
cd88804 to
34eed25
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
This PR tightens GitHub Actions triggers so that editing one workflow file does not unnecessarily trigger other, unrelated workflows. The goal is to reduce CI time and noise when only workflow definitions are being updated.
Changes:
- Update
.github/workflows/test.ymlto addpaths-ignorefilters onpull_requestandpushevents, ignoring changes to thereleaseandbenchmarkworkflows. - Update
.github/workflows/benchmark.ymlto addpaths-ignorefilters onpull_requestandpushevents, ignoring changes to thereleaseandtestworkflows (though the new YAML is currently malformed and will not load).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| .github/workflows/test.yml | Adds paths-ignore for PRs and pushes so the test workflow is skipped when only release.yml or benchmark.yml change. |
| .github/workflows/benchmark.yml | Attempts to add paths-ignore for PRs and pushes so the benchmark workflow is skipped when only release.yml or test.yml change; however, the paths-ignore values are not expressed as a list, making the workflow YAML invalid. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Before this change, updates to the `release` workflow would trigger the `test` and `benchmark` workflows. Tightly scope the path triggers, to limit the number of length of builds.
34eed25 to
563b4fc
Compare
CDThomas
approved these changes
Jan 29, 2026
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.
Before this change, updates to the
releaseworkflow would trigger thetestandbenchmarkworkflows.Tightly scope the path triggers, to limit the number of length of builds.
Ironically, this change will trigger the workflows we are trying to limit triggers on, but that's life in CI, baby.
Acknowledgment
By submitting this pull request, I confirm that CipherStash can use, modify, copy, and redistribute this contribution, under the terms of CipherStash's choice.