Improved Filtering for Changed Rules #874
Merged
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
cameron-dunn-sublime
force-pushed
the
cd.gha-adj
branch
from
474239e to
3f48d44
Compare
cameron-dunn-sublime
force-pushed
the
cd.gha-adj
branch
from
775323c to
0500de6
Compare
cameron-dunn-sublime
changed the title
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.
Old logic didn't understand changes that weren't affecting rule logic, such as renames and tag changes. I moved further off of
tj-actions/changed-filesbecause I'm not sure how well it's handlingpull_request_targetevents and it just generally is more obfuscated than what we're doing now -- mostly just comparingsource.