Skip to content

Conversation

@rabbitstack
Copy link
Owner

What is the purpose of this PR / why it is needed?

Changed the changed-files action input only to consider modified files.

What type of change does this PR introduce?


Uncomment one or more /kind <> lines:

/kind feature (non-breaking change which adds functionality)

/kind bug-fix (non-breaking change which fixes an issue)

/kind refactor (non-breaking change that restructures the code, while not changing the original functionality)

/kind breaking (fix or feature that would cause existing functionality to not work as expected

/kind cleanup

/kind improvement

/kind design

/kind documentation

/kind other (change that doesn't pertain to any of the above categories)

Any specific area of the project related to this PR?


Uncomment one or more /area <> lines:

/area instrumentation

/area telemetry

/area rule-engine

/area filters

/area yara

/area event

/area captures

/area alertsenders

/area outputs

/area rules

/area filaments

/area config

/area cli

/area tests

/area ci

/area build

/area docs

/area deps

/area other

Special notes for the reviewer


Does this PR introduce a user-facing change?


@rabbitstack rabbitstack added the ci Anything CI (Continuous Integration) related label Mar 19, 2025
@rabbitstack rabbitstack force-pushed the only-consider-modified-rules branch from 0d653ab to f92279e Compare March 19, 2025 17:55
tj-actions/changed-files action should only consider existing rules that have changed.
@rabbitstack rabbitstack merged commit 97e1faa into master Mar 19, 2025
12 of 13 checks passed
@rabbitstack rabbitstack deleted the only-consider-modified-rules branch March 19, 2025 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Anything CI (Continuous Integration) related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants