Docs for marking a batched BG migration finished
What does this MR do and why?
This MR adds a section for force-marking a BG migration finished in case it's broken.
Related to: #393216 (closed)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Merge request reports
Activity
assigned to @ahegyi
- A deleted user
added documentation label
1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/update/background_migrations.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
added 1 commit
- cda04c4b - Docs for marking a batched BG migration finished
changed milestone to %15.10
added typebug label
added sectiondev label
added database label
- A deleted user
added databasereview pending label
mentioned in merge request !113253 (merged)
- Resolved by Adam Hegyi
Hi, @krasio! Could you review this documentation change?
requested review from @krasio
mentioned in issue #393216 (closed)
Setting label groupoptimize based on
@ahegyi
's group.added groupoptimize label
- Resolved by Amy Qualls
- Resolved by Adam Hegyi
added 1 commit
- d27ad3d0 - Docs for marking a batched BG migration finished
added devopsplan label
added 1 commit
- a43270cd - Docs for marking a batched BG migration finished
added 1 commit
- 38057509 - Docs for marking a batched BG migration finished
added databaseapproved label and removed databasereview pending label
requested review from @aqualls
added Technical Writing label
added docs-channel label
added docsimprovement maintenancerefactor typemaintenance labels and removed typebug label
- Resolved by Amy Qualls
added 1 commit
- 30a5efb0 - Docs for marking a batched BG migration finished
- Resolved by Amy Qualls
enabled an automatic merge when the pipeline for 86efeeb8 succeeds
@ahegyi I tried to fix the issue with syntax highlighting in this page, but one of the code examples is likely the cause. I'm walking away and pretending I didn't see it. I've added labels, approved, and am setting MWPS.
Hello @ahegyi
The database team is looking for ways to improve the database review process and we would love your help!
If you'd be open to someone on the database team reaching out to you for a chat, or if you'd like to leave some feedback asynchronously, just post a reply to this comment mentioning:
@gitlab-org/database-team
And someone will be by shortly!
Thanks for your help!
This message was generated automatically. You're welcome to improve it.
mentioned in commit 688d033a
I'll mark this as Pick into 15.9 since it might be needed for users dealing with #393216 (closed). Thanks!
added Pick into 15.9 label
picked the changes into the branch
15-9-stable-ee-patch-3
with commit befacdf2Automatically picked into !114005 (merged), will merge into
15-9-stable-ee
ready for15.9.3-ee
.removed Pick into 15.9 label
mentioned in commit befacdf2
mentioned in merge request !114005 (merged)
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label