Issues relating to release management (new GitLab release, Ruby gems, etc).

Deprecation and removal of a functionality when it's no longer needed

Modification to improve the scalability of GitLab that is not a user facing change or performance improvement

Test coverage improvements that were not included in feature prioritization.

General improvements to product usability that are unrelated to feature prioritization

Issues and merge request related to improvements to the engineering workflow automation

Issues that show up in the Major Wins Wishlist on our direction page

Map business value, people, processes, and data across value streams.

Issues related to GitLab Flavored Markdown: https://docs.gitlab.com/ee/user/markdown.html

master-broken incidents caused by caching issues

master-broken incidents caused by a bug in the CI configuration

master-broken incident caused by dependency upgrades to Ruby version, Node version, gem versions, etc..

This is to indicate master broken incidents caused by external dependency issues such as npm registry down, RubyGems.org down, etc.

This label represents a broken master pipeline caused by failing to pull docker image from the image registry.

master-broken incidents caused by flaky tests

master-broken incidents occurred in fork repos, main FOSS and JiHu, due to code changes to the Gitlab main repo that does not have any test coverage for running in a fork repo.

This label is for master broken incidents occured because gitaly is failed to setup. See example: gitlab-org/quality/engineering-productivity/master-broken-incidents#625

This label describes a broken master scenario with the error "Gitlab is unable to handle this request due to load."

master-broken incidents caused by various infrastructure issue such as network error, runner memory limit reached, etc.

This label is to identify master broken incidents caused by job timing out