Labels

(Large) Features that are well understood, but known to be hard. Bugs that are very poorly understood, and will not have a suggested solution.

Track the gamedays as part of DR exercise

Use this label for changes that are an act of tending to your software garden. https://blog.codinghorror.com/tending-your-software-garden/ 🌹💐💐🌸🎄🌺🍀🌷🌻🌲☘️🥀🌼🌿🌴🌱🌳🍂🍃🌵🍄🪻🪴🫚🎍🫛🌾

Competitive roadmap review issues related to GitHub

Issues for the gitlab-releases gem

For changes generated automatically by the GitLab Translation Service, also referred to as Argo-GitLab integration https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/gitlab_translation_service/

tracking projects for women and women identifying team members at GitLab

Directly impacts the performance of gitlab.com. Should be combined with a `Pn` priority label for.

Run full mock goreleaser release (SBOM, signing, docker). See https://gitlab.com/gitlab-com/gl-infra/common-ci-tasks/-/blob/main/goreleaser.md#performing-a-full-mock-release

https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/production-engineering/cloud-cost-utilization/

https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/production-engineering/fleet-management/

https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/production-engineering/runners-platform/

https://handbook.gitlab.com/handbook/engineering/infrastructure/team/runway/