[Feature flag] Enable gpg_signing feature flag
What
Enable the :gitaly_gpg_signing
feature flag. This flag enables Gitaly to use the new gitaly-gpg
binary to sign commits.
Owners
- Team: Gitaly
- Most appropriate slack channel to reach out to:
#g_gitaly
- Best individual to reach out to: @jcaigitlab
Expectations
What release does this feature occur in first?
16.2
What are we expecting to happen?
Nothing on gitlab.com, since we don't have the signing_key
configured. But on self service customers, commit signing should work if the feature flag is turned on.
What might happen if this goes wrong?
commit signing ends up signing commits incorrectly.
What can we monitor to detect problems with this?
- Open https://dashboards.gitlab.net/d/000000199/gitaly-feature-status
- Change "method" to
UserMergeBranch
- Copy/paste the URL & change gprd to gstd to monitor staging as well as prod
Roll Out Steps
-
Enable on staging
- Is the required code deployed on staging? (howto)
- Enable on staging (howto)
- Add featureflagstaging to this issue (howto)
- Test on staging (howto)
-
Verify the feature flag was used by checking Prometheus metric
gitaly_feature_flag_checks_total
-
Enable on production
- Is the required code deployed on production? (howto)
- Progressively enable in production (howto)
- Add featureflagproduction to this issue
-
Verify the feature flag was used by checking Prometheus metric
gitaly_feature_flag_checks_total
-
Default-enable the feature flag (optional, only required if backwards-compatibility concerns exist)
- Wait for release containg default-disabled feature flag.
- Change the feature flag to default-enabled (howto)
- Wait for release containing default-enabled feature flag.
- Remove feature flag
Please refer to the documentation of feature flags for further information.
- Show closed items
Is blocked by
- gitlab #439980Backlog
Relates to
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- John Cai marked the checklist item Enable on staging as completed
marked the checklist item Enable on staging as completed
- John Cai marked the checklist item Add featureflagstaging to this issue (howto) as completed
marked the checklist item Add featureflagstaging to this issue (howto) as completed
- John Cai marked the checklist item Verify the feature flag was used by checking Prometheus metric
gitaly_feature_flag_checks_total
as completedmarked the checklist item Verify the feature flag was used by checking Prometheus metric
gitaly_feature_flag_checks_total
as completed - John Cai removed featureflagdisabled label
removed featureflagdisabled label
- John Cai added featureflagstaging label
added featureflagstaging label
- John Cai marked the checklist item Enable on production as completed
marked the checklist item Enable on production as completed
- John Cai marked the checklist item Add featureflagproduction to this issue as completed
marked the checklist item Add featureflagproduction to this issue as completed
- John Cai marked the checklist item Verify the feature flag was used by checking Prometheus metric
gitaly_feature_flag_checks_total
as completedmarked the checklist item Verify the feature flag was used by checking Prometheus metric
gitaly_feature_flag_checks_total
as completed - John Cai removed featureflagstaging label
removed featureflagstaging label
- John Cai added featureflagproduction label
added featureflagproduction label
- Patrick Steinhardt assigned to @jcaigitlab
assigned to @jcaigitlab
- Patrick Steinhardt changed milestone to %16.4
changed milestone to %16.4
- Maintainer
@jcaigitlab What is the state of this feature flag? Can we remove it from Gitaly?
Collapse replies - Author Maintainer
@igor.drozdov do you know the plans for adding a key to sign in production? I'd like to wait until we verify this works in production before we remove the feature flag.
- Developer
I'd like to wait until we verify this works in production before we remove the feature flag.
Yes, let's wait until it's configured on production
do you know the plans for adding a key to sign in production?
Yes, since the key rotation merge request is merged, I'll create an issue to enable it on production
- Author Maintainer
@igor.drozdov could you link that issue here? thanks!
1 - Developer
@jcaigitlab the production has been configured and the feature flag has been enabled for
gitlab-org/gitlab
,gitlab-org/gitaly
andgitlab-org/gitlab-shell
.I'll monitor and then start enabling it globally, then let's wait for some time for feedback: for a week, for example, until I'm back from OOO (11 Sep). Then we can go ahead and remove the feature flag if everything is fine
- Author Maintainer
sounds good, thank you @igor.drozdov! I'll go ahead and assign this issue to you then since you've been doing all the work
- Patrick Steinhardt added maintenanceremoval typemaintenance labels
added maintenanceremoval typemaintenance labels
- Andras Horvath added workflowin dev label
added workflowin dev label
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#13860 (closed)
mentioned in issue gitlab-org/quality/triage-reports#13860 (closed)
- John Cai assigned to @igor.drozdov
assigned to @igor.drozdov
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#13979 (closed)
mentioned in issue gitlab-org/quality/triage-reports#13979 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#14077 (closed)
mentioned in issue gitlab-org/quality/triage-reports#14077 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#14146 (closed)
mentioned in issue gitlab-org/quality/triage-reports#14146 (closed)
- 🤖 GitLab Bot 🤖 changed milestone to %16.5
changed milestone to %16.5
- 🤖 GitLab Bot 🤖 added missed:16.4 label
added missed:16.4 label
- Author Maintainer
@igor.drozdov can we consider this issue complete, and do you think we can go ahead and remove the feature flag?
Collapse replies - Developer
@jcaigitlab unfortunately, we had to disable the feature flag: gitlab#19185 (comment 1570735262)
I'll investigate the potential fixes
@hmatthews et al. It would be great to see an epic for the outstanding work in this area. We have been waiting for commit signing for a long time now, and it's hard to see what work remains before this is GA. Thanks
1- Developer
- Author Maintainer
@igor.drozdov with !6558 (merged), would we be able to turn this back on?
- Developer
@igor.drozdov bumping again here.
- Developer
@knayakgl @jcaigitlab
sorry for the delay here, this feature flag hasn't been enabled globally (only for Gitlab projects). After discussing it in this issue Specify GitLab as a Committer for commits creat... (#5715 - closed), my plan was to allow users to disable the functionality per project and then the feature flag can be removed. But I didn't have a chance to implement it - Author Maintainer
thanks @igor.drozdov! so it sounds like we'll keep this feature flag around for now until the feature is implemented.
my plan was to allow users to disable the functionality per project and then the feature flag can be removed.
is there an issue you can link?
- Developer
@jcaigitlab I've created an issue for it, all the progress can be tracked there Add controls to allow groups to opt in to web-b... (gitlab#439980)
1
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#14240 (closed)
mentioned in issue gitlab-org/quality/triage-reports#14240 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#14354 (closed)
mentioned in issue gitlab-org/quality/triage-reports#14354 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#14446 (closed)
mentioned in issue gitlab-org/quality/triage-reports#14446 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#14517 (closed)
mentioned in issue gitlab-org/quality/triage-reports#14517 (closed)
- 🤖 GitLab Bot 🤖 changed milestone to %16.6
changed milestone to %16.6
- 🤖 GitLab Bot 🤖 added missed:16.5 label
added missed:16.5 label
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#14612 (closed)
mentioned in issue gitlab-org/quality/triage-reports#14612 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#14678 (closed)
mentioned in issue gitlab-org/quality/triage-reports#14678 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#14796 (closed)
mentioned in issue gitlab-org/quality/triage-reports#14796 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#14892 (closed)
mentioned in issue gitlab-org/quality/triage-reports#14892 (closed)
- 🤖 GitLab Bot 🤖 changed milestone to %16.7
changed milestone to %16.7
- 🤖 GitLab Bot 🤖 added missed:16.6 label
added missed:16.6 label
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#14962 (closed)
mentioned in issue gitlab-org/quality/triage-reports#14962 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#15058 (closed)
mentioned in issue gitlab-org/quality/triage-reports#15058 (closed)
- Igor Drozdov mentioned in issue #5715 (closed)
mentioned in issue #5715 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#15172 (closed)
mentioned in issue gitlab-org/quality/triage-reports#15172 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#15267 (closed)
mentioned in issue gitlab-org/quality/triage-reports#15267 (closed)
- Igor Drozdov mentioned in issue gitlab#19185 (closed)
mentioned in issue gitlab#19185 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#15387 (closed)
mentioned in issue gitlab-org/quality/triage-reports#15387 (closed)
- 🤖 GitLab Bot 🤖 changed milestone to %16.8
changed milestone to %16.8
- 🤖 GitLab Bot 🤖 added missed:16.7 label
added missed:16.7 label
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#15483 (closed)
mentioned in issue gitlab-org/quality/triage-reports#15483 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#15550 (closed)
mentioned in issue gitlab-org/quality/triage-reports#15550 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#15691 (closed)
mentioned in issue gitlab-org/quality/triage-reports#15691 (closed)
- Andras Horvath changed milestone to %16.9
changed milestone to %16.9
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#15815 (closed)
mentioned in issue gitlab-org/quality/triage-reports#15815 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#15888 (closed)
mentioned in issue gitlab-org/quality/triage-reports#15888 (closed)
- 🤖 GitLab Bot 🤖 added group::gitalygit label
added group::gitalygit label
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#15998 (closed)
mentioned in issue gitlab-org/quality/triage-reports#15998 (closed)
- Igor Drozdov marked this issue as blocked by gitlab#439980
marked this issue as blocked by gitlab#439980
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#16168 (closed)
mentioned in issue gitlab-org/quality/triage-reports#16168 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#16271 (closed)
mentioned in issue gitlab-org/quality/triage-reports#16271 (closed)
- 🤖 GitLab Bot 🤖 changed milestone to %16.10
changed milestone to %16.10
- 🤖 GitLab Bot 🤖 added missed:16.9 label
added missed:16.9 label
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#16354 (closed)
mentioned in issue gitlab-org/quality/triage-reports#16354 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#16460 (closed)
mentioned in issue gitlab-org/quality/triage-reports#16460 (closed)
- Igor Drozdov mentioned in issue gitlab#326775
mentioned in issue gitlab#326775
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#16629 (closed)
mentioned in issue gitlab-org/quality/triage-reports#16629 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#16730 (closed)
mentioned in issue gitlab-org/quality/triage-reports#16730 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#16813 (closed)
mentioned in issue gitlab-org/quality/triage-reports#16813 (closed)
- 🤖 GitLab Bot 🤖 changed milestone to %16.11
changed milestone to %16.11
- 🤖 GitLab Bot 🤖 added missed:16.10 label
added missed:16.10 label
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#16919 (closed)
mentioned in issue gitlab-org/quality/triage-reports#16919 (closed)
- Developer
I have a GitLab Dedicated customer who is very interested in GPG key signing for Gitaly, but I understand work to support this feature in Dedicated is dependent on enabling this FF by default.
@igor.drozdov @jcaigitlab what is the confidence level in this making 16.11?
Collapse replies - Developer
@lstahlman let me add a bit of context:
Every time a user creates a commit via Web or creates a merge/squash commit, etc, Gitaly creates a commit on behalf of a user. It means that a user doesn’t create a commit locally and pushes it.
When a user creates a commit locally, signs it and pushes it, the user uses their own private key to sign the commit. Since Gitaly doesn’t (and shouldn’t) have access to the private key, Gitaly uses its own key configured instance-wide. And we have implemented this functionality a while ago.
Currently, when a user creates a commit via Web, the Author and Committer field are both set to the user’s data User Name user@email.com. But, when we started rolling it out, we received feedback and realized that it makes sense to set the Committer field of the commit to the GitLab noreply@gitlab.com. We’ve implemented this change and it turned out to be a breaking change that caused a lot of issues.
This issue https://gitlab.com/gitlab-org/gitlab/-/issues/452078+ is caused by the Committer field change as well.
However, it’s possible to configure the behavior when the commits are signed, but the Committer field is still set to the user’s data:
- The customers can configure which name and email is set to the web commits
- If this config option is not set, then the current behavior is applied: Committer field is set to the user data
It means we’ll have the current behavior but with signed commits. So I wonder if it’s something that we can move forward with in the customer case?
We’ll unlikely be able to cover all the edge-cases in %16.11 that we have with the committer field and the fact that they are related to security makes it’s even riskier. But we can enable the feature flag by default and disable it for .com (as we do for git-guardian feature flag). Self-managed won’t see any difference because enabling a feature flag is not enough to enable the commit signing, the instance must be configured as well.
- Author Maintainer
@lstahlman This is currently blocked on gitlab#439980 due to security concerns. That issue is in the backlog, so I'm afraid we won't make the %16.11 milestone.
If a dedicated customer is interested, that may justify bringing gitlab#439980 out of the backlog so that we can proceed with the feature flag rollout.
@andr3 given the interest from a Dedicated customer, could we get schedule gitlab#439980?
/cc @igor.drozdov
Collapse replies - Developer
@andr3 is on PTO (See PTO issue) and @jwoodwardgl is the primary contact for Engineering Support groupsource code Backend.
@jwoodwardgl could you please see if we can get Add controls to allow groups to opt in to web-b... (gitlab#439980) scheduled in %16.11?
/cc @igor.drozdov
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#16998 (closed)
mentioned in issue gitlab-org/quality/triage-reports#16998 (closed)
- Igor Drozdov mentioned in merge request !6795 (merged)
mentioned in merge request !6795 (merged)
- Kai Armstrong mentioned in issue gitlab#439980
mentioned in issue gitlab#439980
- Developer
@mcbabin @derekferguson I've blocked this against https://gitlab.com/gitlab-org/gitlab/-/issues/452078. I'd like to make sure we have a resolution there before rolling this out further.
1 - 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17191 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17191 (closed)
- Kai Armstrong added to epic &13492
added to epic &13492
- Developer
@mcbabin @andr3 @derekferguson @phikai
Status update
-
Add co_authored_by placeholder to suggestions t... (gitlab!148890 - merged) is merged
Merge request suggestions will now addCo-authored-by
trailer whenever necessary to give credits to the users who contributed to a particular suggestion - Change author of cherry-picked commits (!6804 - merged) is a merge request on Gitaly side. It will allow us to control Author field of cherry-picked commits. It will enable us to change the behavior of that field via GitLab Rails code. The merge request is currently being reviewed.
- Set the user who creates web commit as its author (gitlab!148889 - merged) is being reviewed and in my opinion is close to being merged. However, it's blocked by the Gitaly merge request above. After this MR is merged, we'll start gradually enabling the new Committer field behavior and signing.
If you need me to clarify anything or you would prefer a different place for status updates, feel free to ping me.
2 2 -
Add co_authored_by placeholder to suggestions t... (gitlab!148890 - merged) is merged
Collapse replies - Developer
Thank you so much for the continued work here @igor.drozdov!
1 - Developer
Thank you for your continued efforts on moving this forward @igor.drozdov!
- Developer
@mcbabin @phikai the MRs are merged, thanks to the speedy reviews of the team!
Just FYI, based on https://gitlab.slack.com/archives/C0XM5UU6B/p1712945341938129 they may even get into 16.11 but as untested functionality behind disabled feature flags. This Slack thread also mentions the following:
It needs to be deployed to production at latest monday EST afternoon, assuming there are no incidents barring deployments to production.
The MRs are deployed on production, but I haven't tried enabling the feature flags yet to avoid incidents today. I'll start enabling it in the evening or tomorrow
- Developer
@igor.drozdov IMO, I don't think we should target turning this on at this time, I think we need to continue assessing things before we look at a wider rollout. It's up to @mcbabin, but want to make sure that I voice that I still have concerns here.
- Developer
@phikai my plan is to focus on enabling
web_ui_commit_author_change
first. This feature flag is responsible for theAuthor
field changes described in Set the user who creates web commit as its author (gitlab!148889 - merged). It won't setCommitter
field toGitLab <>
for now - Developer
@igor.drozdov Can you turn that on for
phikai/my-public-test-project
id: 12678598 - Developer
@phikai done https://gitlab.slack.com/archives/C101F3796/p1713198025621829
I've enabled onlyweb_ui_commit_author_change
FF for your project, commit signing hasn't been enabled for your project yet (please let me know if it should be).I've enabled all the feature flags on Staging and have a group with push rules feature available: https://staging.gitlab.com/source-code-management-test-group/commit-signing-test. I can also add you if needed
@mcbabin I've noticed that you are not in the group, added 1 - Developer
@igor.drozdov I enabled the commit signing on my project before, so it should have everything turned on.
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17271 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17271 (closed)
- 🤖 GitLab Bot 🤖 changed milestone to %17.0
changed milestone to %17.0
- 🤖 GitLab Bot 🤖 added missed:16.11 label
added missed:16.11 label
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17347 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17347 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17446 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17446 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17613 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17613 (closed)
- Marie-Christine Babin mentioned in merge request gitlab-com/www-gitlab-com!134296 (merged)
mentioned in merge request gitlab-com/www-gitlab-com!134296 (merged)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#17716 (closed)
mentioned in issue gitlab-org/quality/triage-reports#17716 (closed)
- 🤖 GitLab Bot 🤖 changed milestone to %17.1
changed milestone to %17.1
- 🤖 GitLab Bot 🤖 added missed:17.0 label
added missed:17.0 label
- Developer
- Igor Drozdov unassigned @igor.drozdov
unassigned @igor.drozdov
- Igor Drozdov changed milestone to %Next 4-6 releases
changed milestone to %Next 4-6 releases
@jcaigitlab @hmatthews We have commit signing working in our self-managed instance now, but I've just had a user report that rebase from the UI creates unsigned commits. Is this a know issue that we can track, or do we need to raise a new issue?
1Collapse replies - Developer
@jonmngc thats expected behavior and something that’s being clarified in the documentation in gitlab!153392 (merged).
@jonmngc @phikai I can't find any public discussion on why the rebase behavior has changed (IIRC it worked in older releases with the FF on), but I'm guessing this is taking a page out of GitHub's book (here) and understandably staying on the safe side, as rebasing essentially would re-sign on others' behalf. By rebasing locally, the user takes responsibility for that.
But, for some workflows/self-hosted instances this would still be desired, as it makes end-to-end enforcement of signed commits feasible again. Is there any chance that this would still be considered perhaps behind an admin-level guard? As with web commits, these instances may have a level of confidence that rebases done in the UI are already done with 2FA and so on.
Maybe adding a git trailer that makes it clearer that the commit was "signed by ... on behalf of ..." or similar would make this more feasible as well.
Edited by Nejc Habjan- Developer
@nejc I'll defer to @igor.drozdov on whether or not it ever worked or is possible. I suspect because of the way a rebase works under the hood within GitLab, it's potentially not possible at all, but that's just speculation on my part.
cc: @mcbabin
1 Thanks @phikai - looking at my old notes (we've had the FF enabled for a while on our dev instance) it seems like this used to work but there was probably some discussion around committer/author that influenced this as well. Happy to get more feedback though, thanks a lot for the quick response!
2- Developer
@igor.drozdov Hi there are you able to add anything to the comment from @phikai above?
Cheers
- Developer
@hmatthews @phikai thanks for the ping and @nejc thanks for the questions
Signing commits on rebase doesn't work and as far as I remember never worked. Maybe it did in the very beginning within this MR: feat(gitaly-git2go): sign commits with OpenPGP key (!4802 - merged), but it changed around ~16.0 release.
It is technically possible but is not implemented due to the reasons listed: #5361 (comment 1918471417)
2
- 🤖 GitLab Bot 🤖 changed milestone to %17.3
changed milestone to %17.3
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19089 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19089 (closed)
- 🤖 GitLab Bot 🤖 changed milestone to %17.4
changed milestone to %17.4
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19201 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19201 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19287 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19287 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19371 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19371 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19542 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19542 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19657 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19657 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19669 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19669 (closed)
- 🤖 GitLab Bot 🤖 changed milestone to %17.5
changed milestone to %17.5
- 🤖 GitLab Bot 🤖 changed milestone to %17.5
changed milestone to %17.5
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19806 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19806 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19916 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19916 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#19998 (closed)
mentioned in issue gitlab-org/quality/triage-reports#19998 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#20132 (closed)
mentioned in issue gitlab-org/quality/triage-reports#20132 (closed)
- 🤖 GitLab Bot 🤖 changed milestone to %17.6
changed milestone to %17.6
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#20247 (closed)
mentioned in issue gitlab-org/quality/triage-reports#20247 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#20329 (closed)
mentioned in issue gitlab-org/quality/triage-reports#20329 (closed)
- Andreas mentioned in issue gitlab#296571 (closed)
mentioned in issue gitlab#296571 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#20445 (closed)
mentioned in issue gitlab-org/quality/triage-reports#20445 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#20582 (closed)
mentioned in issue gitlab-org/quality/triage-reports#20582 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#20750 (closed)
mentioned in issue gitlab-org/quality/triage-reports#20750 (closed)
- 🤖 GitLab Bot 🤖 changed milestone to %17.7
changed milestone to %17.7
- 🤖 GitLab Bot 🤖 changed milestone to %17.7
changed milestone to %17.7
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#20830 (closed)
mentioned in issue gitlab-org/quality/triage-reports#20830 (closed)
- John Cai added devopsdata_access label and removed devopssystems label
added devopsdata_access label and removed devopssystems label
- John Cai added sectioninfrastructure platforms label and removed sectioncore platform label
added sectioninfrastructure platforms label and removed sectioncore platform label
- 🤖 GitLab Bot 🤖 changed milestone to %17.8
changed milestone to %17.8
- 🤖 GitLab Bot 🤖 changed milestone to %17.8
changed milestone to %17.8
- 🤖 GitLab Bot 🤖 changed milestone to %17.9
changed milestone to %17.9
- 🤖 GitLab Bot 🤖 changed milestone to %17.10
changed milestone to %17.10
- James Fargher mentioned in issue #6632 (closed)
mentioned in issue #6632 (closed)
- Kai Armstrong changed milestone to %Backlog
changed milestone to %Backlog
- 🤖 GitLab Bot 🤖 changed milestone to %17.10
changed milestone to %17.10