Modifing pipeline checks to only trigger on specific file changes#138
Merged
maernest04 merged 1 commit intomainfrom May 5, 2026
Merged
Conversation
steeevin88
approved these changes
May 4, 2026
Contributor
steeevin88
left a comment
steeevin88
left a comment
There was a problem hiding this comment.
looks fine to me, fix the typo in the PR title + we can merge
maernest04
force-pushed
the
ernest_ma/run_pipelines_on_specific_changes
branch
from
46bab68 to
0bcf1f2
Compare
Testing lint.yml Testing go-ci.yml Fixing read me after adding yml changes
maernest04
force-pushed
the
ernest_ma/run_pipelines_on_specific_changes
branch
from
0bcf1f2 to
c75d2ac
Compare
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.
PR for #130
Problem
Heavy CI (lint, Go build/tests, Docker integration) ran on every PR, even if its simple PR changes like read me's. We should only run CI's on relevant file changes.
Solution
Add path-based change detection to the SCEvents workflows so those jobs only run when relevant files change, and add always-green status jobs so merge checks still pass when a workflow is intentionally skipped.