Move CI rules-changes to an entry class
What does this MR do and why?
This is the first step of improving the rules:changes CI config.
This MR just moves it to its own entry class.
Related to #293645 (closed)
In the next steps, paths and compare will be added to rules:changes.
| Step | Status |
|---|---|
| 1. Move CI rules-changes to an entry class |
|
| 2. Refactor CI rules entry to use composed value | !90238 (merged) |
3. Add rules:changes:paths alias to rules:changes
|
!90171 (merged) |
4. Implement rules:changes:compare
|
!90968 (merged) |
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Furkan Ayhan