Resolve "API Support for Immediate Group Deletion"
What does this MR do?
Adding documentation for changes done in delete group API in !92508 (merged).
Related issues
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added. -
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. -
Ensure a release milestone is set. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Merge request reports
Activity
changed milestone to %15.3
added 1 commit
- fd2d6dc4 - Adding description for immediate deletion of subgroup
Suggested Reviewers (beta)
The individuals below may be good candidates to participate in the review based on various factors.
You can use slash commands in comments to quickly assign
/assign_reviewer @user1
.Suggested Reviewers @rymai
,@smcgivern
,@stanhu
,@axil
,@tkuah
If you do not believe these suggestions are useful, please apply the label Bad Suggested Reviewer. You can also provide feedback for this feature on this issue:
https://gitlab.com/gitlab-org/gitlab/-/issues/357923
.Automatically generated by Suggested Reviewers Bot - an experimental ML-based recommendation engine created by ~"group::applied ml".
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/api/groups.md
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
Dangeradded docsimprovement maintenancerefactor labels
assigned to @hraghuvanshi
added typemaintenance label and removed featureaddition typefeature labels
marked the checklist item If you are a GitLab team member, request a review based on: as completed
mentioned in merge request gitlab-com/www-gitlab-com!106489 (merged)
requested review from @fneill
@fneill Can you please review this?
- Resolved by Hitesh Raghuvanshi
- Resolved by Hitesh Raghuvanshi
- Resolved by Hitesh Raghuvanshi
- Resolved by Hitesh Raghuvanshi
Thanks @hraghuvanshi! Just a couple review comments from myself, over to you
added Technical Writing label
added 1 commit
- ac2f2371 - Applying suggestions as per API style guide.
- Resolved by Fiona Neill
@hraghuvanshi I just noticed in the MR for this change that there's also
immediate_delete_subgroup_api
that's being deployed behind a feature flag. Should there be documentation added for that too?
added 245 commits
-
c77269e2...510f648f - 237 commits from branch
master
- 34884282 - Adding description for immediate deletion of subgroup
- 2cabba0b - Fixed spelling mistake
- 0da96bc6 - Applying suggestions as per API style guide
- 56636033 - Suggestion for introducing version history
- 604095ee - Fixed linter error
- 424f7b06 - Fixed linter error
- 4a1e5df4 - Fixed linter error
- a1c2b85f - Suggestion for description
Toggle commit list-
c77269e2...510f648f - 237 commits from branch
removed review request for @fneill
added 853 commits
-
a1c2b85f...cfacf1c5 - 845 commits from branch
master
- c2904053 - Adding description for immediate deletion of subgroup
- 1772ad69 - Fixed spelling mistake
- 542620cc - Applying suggestions as per API style guide
- a4a49ce8 - Suggestion for introducing version history
- 802505ff - Fixed linter error
- e0b16502 - Fixed linter error
- 7ab87a7b - Fixed linter error
- 562edea0 - Suggestion for description
Toggle commit list-
a1c2b85f...cfacf1c5 - 845 commits from branch
changed milestone to %15.4
- Resolved by Hitesh Raghuvanshi
1 Warning This merge request includes more than 10 commits. Each commit should meet the following criteria: - Have a well-written commit message.
- Has all tests passing when used on its own (e.g. when using git checkout SHA).
- Can be reverted on its own without also requiring the revert of commit that came before it.
- Is small enough that it can be reviewed in isolation in under 30 minutes or so.
If this merge request contains commits that do not meet this criteria and/or contains intermediate work, please rebase these commits into a smaller number of commits or split this merge request into multiple smaller merge requests.
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/api/groups.md
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
Dangerrequested review from @fneill
- Resolved by Evan Read
Hi @fneill, the feature flag for this feature has been enabled for all the users. I think we can deploy the document, and can you please review this too.
FYI, I have bumped the milestone to 15.4, is that correct?Edited by Hitesh Raghuvanshi
- Resolved by Hitesh Raghuvanshi
removed review request for @fneill
added 712 commits
-
095d0c5b...9f80b676 - 702 commits from branch
master
- 69d19ca9 - Adding description for immediate deletion of subgroup
- f97e7f90 - Fixed spelling mistake
- c229b54e - Applying suggestions as per API style guide
- f4e3fa7e - Suggestion for introducing version history
- 80a54678 - Fixed linter error
- bff33ea1 - Fixed linter error
- 6b2cd44b - Fixed linter error
- 08656c18 - Suggestion for description
- 74e3412e - Bumping milestone version to 15.4
- 561e9183 - Adding suggestion for feature flag
Toggle commit list-
095d0c5b...9f80b676 - 702 commits from branch
requested review from @eread
- Resolved by Hitesh Raghuvanshi
Hi @eread, can you please review this, since
@fneill
is on leave, she asked me to ask you for this at !95608 (comment 1078179468).
added workflowin review label and removed workflowverification label
- Resolved by Evan Read
- Resolved by Evan Read
- Resolved by Hitesh Raghuvanshi
removed review request for @eread
added 1 commit
- b5d95777 - Adding suggestions for rephrasing introduction
added 210 commits
-
b5d95777...98d8e33e - 198 commits from branch
master
- de41464e - Adding description for immediate deletion of subgroup
- a8d3d1f6 - Fixed spelling mistake
- af4db158 - Applying suggestions as per API style guide
- 8b1118c8 - Suggestion for introducing version history
- 0089ee6b - Fixed linter error
- 20486e11 - Fixed linter error
- bd8a003b - Fixed linter error
- 4447dd83 - Suggestion for description
- 21c838d8 - Bumping milestone version to 15.4
- 757e7cd7 - Adding suggestion for feature flag
- 50eedf74 - Fixed broken link
- e1285339 - Adding suggestions for rephrasing introduction
Toggle commit list-
b5d95777...98d8e33e - 198 commits from branch
added 1 commit
- 7d7940c4 - Adding suggestions for adding release version
requested review from @eread
enabled an automatic merge when the pipeline for c9819dd4 succeeds
mentioned in commit a9e63e7e
mentioned in merge request !96839 (merged)
added workflowstaging-canary label and removed workflowin review label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
added devopsdata stores grouptenant scale sectioncore platform labels and removed devopsmanage sectiondev + 1 deleted label