Fix ci_templates danger rule
Summary
While working on adding a warnning to ci_templates danger rule, I realised that in code we say that these rules are only ci rules but in fact they show in the UI only. Spoke to the teammates and realised it most likely is a bug.
Proposal
- Investigate where the ci_templates danger warnings etc should be visible and fix it in the code.
- Verify the exisiting warnings in the ci_template danger rule to ensure they are still relevant and needed.
- Verify if any docs will need to be updated.
Confirm purpose and User Reception (how does this benefit the user?)
When we modify the ci_templates, we should be able to see danger warnings in the CI and the UI to increase changes them being adressed. Ensuring the danger rule is up to date is crucial for the ci templates maintenance.
Additional details
See a comment with more details.
Some relevant technical details, if applicable, such as:
- Does this need a feature flag?
- Does there need to be an associated instrumentation issue created related to this work?
- Is there an example response showing the data structure that should be returned (new endpoints only)?
- What permissions should be used?
- Is this EE or CE?
-
EE -
CE
-
- Additional comments:
Documentation
Some docs might need an update.
Links/References
Edited by Kasia Misirli