Labels

The goal this milestone is to have: the engineering implementation plan for this issue created, a weight applied, and any priority or workflow labels added. If needed, this should be reviewed and approved by another engineer and/or product.

This issue is an inspirational goal for this milestone. If we can work on it, great, if not then we'll schedule it for another milestone.

Issues for Ruby teams that require some knowledge of Go, because they may require changes in Gitaly, Workhorse, etc

Mitigate risks in large enterprises, including (but not limited to) enforced workflows, approvals, templating of various artifacts like issues and code files, compliance, traceability of requirements, and auditing/logging.

Relates to the gpg verification feature for commits introduced in v9.5: https://docs.gitlab.com/ce/user/project/gpg_signed_commits/

Issues related to the project Graphs pages

Related to group importing.

&332

Work related to the Infrastructure Production Engineering Networking & Incident Management team.

Dedicated US PubSec group label used to identify issues, MRs, epics owned by the US PubSec group in GitLab Dedicated stage

Issues belonging to the Acquisition group of the Growth stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#acquisition-group

Issues belonging to the Activation group of the Growth stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#activation-group