Add .rubocop_manual_todo.yml to code patterns
What does this MR do?
When we added .rubocop_manual_todo.yml
in !46477 (merged) we missed to add it to code patterns in our CI yaml so the pipeline looks very light if an MR contains changes only in .rubocop_manual_todo.yml
.
Example !47549 (merged)
Verification
The MR !47557 (closed) demonstrates the before and after we add .rubocop_manual_todo.yml
to code patterns.
Before (target master ) |
After (target pl-add-rubocop-manual-todo-rules ) |
---|---|
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
- [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
- [-] Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec
- [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team
Edited by Peter Leitzen