Labels
Prioritized labels 20
Drag to reorder prioritized labels and change their relative priority.
-
congregateAzure DevOps Migration SupportGitLab.org / Professional Services Automation / Tools / Migration
-
congregateBitBucket Migration SupportGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregateCustomerGitLab.org / Professional Services Automation / Tools / Migration / CongregateIssues that are related to customer requests (feature of migration specific)
-
congregateDocsGitLab.org / Professional Services Automation / Tools / Migration / CongregateIssues involving documentation updates
-
congregateGitHub Migration SupportGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny issues related to support a GitHub/GHE migration to scale
-
congregateJenkins Variable Migration SupportGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregateLDAP migration supportGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny issue related to migrating LDAP configurations into GitLab
-
congregateNew FeatureGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny new feature or improvement for congregate
-
congregateGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregate::New FeatureconfigurationGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny new feature or improvement related to configuring congregate
-
congregate::New Featurelisting dataGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny new feature or improvement related to retrieving data from a source instance
-
congregate::New Featurestaging dataGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny new feature or improvement related to staging data for a migration
-
congregateSVN migration supportGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregateTFS SupportGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny issue related to supporting TFS to Git migrations
-
congregateTeamCity Variable Migration SupportGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregateTechnical DebtGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny issue created as a result of not addressing something during a fire-fight
-
congregateUI Refactor MVC 1GitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregatebugGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregatee2e-testGitLab.org / Professional Services Automation / Tools / Migration / Congregate
-
congregatesupportGitLab.org / Professional Services Automation / Tools / Migration / CongregateAny issue created by a user of congregate looking for support from the congregate development team
Labels 3,621
-
pipeline abuse preventionGitLab.orgPipeline Abuse Prevention PVS part of the Anti-Abuse group of the Anti-abuse Stage
-
pipeline processingGitLab.orgIssues related to the execution of pipeline jobs, including DAG, child pipelines, and matrix build jobs.
-
pipeline visualizationsGitLab.orgIssues related to visualization of CI pipelines, including pipeline graphs, pipeline dependencies for triggers, cross-project pipelines, and child/parent pipelines.
-
pipelineexpeditedGitLab.orgSet this label on "master fixing" or urgent revert MRs to skip Review Apps and QA related jobs
-
pipelinetier-1GitLab.orgTier 1 pipelines are run when a merge request has no approvals. See gitlab-org/quality/engineering-productivity&58 for more info.
-
pipelinetier-2GitLab.orgTier 2 pipelines are run when a merge request has at at least one approval, but still requires more approvals. See gitlab-org/quality/engineering-productivity&58 for more info.
-
pipelinetier-3GitLab.orgTier 3 pipelines are run when a merge request has all the approvals it needs. See gitlab-org/quality/engineering-productivity&58 for more info.
-
pipeline:force-run-as-if-jhGitLab.orgForce as-if-jh pipeline to run even when it's disabled by $CI_AS_IF_JH_ENABLED. See ~"pipeline:run-as-if-jh" for details
-
pipeline:mr-approvedGitLab.orgIndicates that associated merge request pipelines will be forced to run non-minimal sets of RSpec and Jest tests. More info at https://docs.gitlab.com/ee/development/pipelines/index.html#rspec-minimal-jobs and https://docs.gitlab.com/ee/development/pipelines/index.html#jest-minimal-jobs
-
pipeline:run-CS-evaluationGitLab.orgAssociated merge request pipelines will include a multi-project pipeline to evaluate Code Suggestions via https://gitlab.com/gitlab-com/create-stage/code-creation/code-suggestion-scenarios/
-
pipeline:run-all-jestGitLab.orgIndicates that associated merge request pipelines will be forced to run all the jest jobs to regardless of the changes
-
pipeline:run-all-rspecGitLab.orgIndicates that associated merge request pipelines will be forced to run all the RSpec jobs to regardless of the changes
-
pipeline:run-as-if-fossGitLab.orgIndicates that associated merge request pipeline jobs would run in the context of the `gitlab-org/gitlab-foss` project
-
pipeline:run-as-if-jhGitLab.orgIndicates that associated merge request pipeline will trigger a cross project downstream pipeline in GitLab JH validation project. See https://docs.gitlab.com/ee/development/pipelines/#as-if-jh-cross-project-downstream-pipeline Can be disabled by setting $CI_AS_IF_JH_ENABLED to `false`