Labels

Non-defect performance improvements such as load time for a specific page or component, or run time for a specific process.

Issues and merge request related to pipeline implementation or improvements

Issues related to things that need improvement and that have been left behind due to high velocity of development

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.

Use Category::Markdown instead

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.

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

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