### Problem to solve We currently do not count chatops pipelines as part of usage data and thus have no way to track feature usage. ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal 1. Introduce a new pipeline type such as `ci_chatops_pipeline` to measure usage of the feature. 1. Add to `usage.rb` ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references