Skip to content
Snippets Groups Projects

Resolve "API Support for Immediate Group Deletion"

All threads resolved!

What does this MR do?

Adding documentation for changes done in delete group API in !92508 (merged).

Related issues

#360008 (closed)

Author's checklist

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 like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure 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.
Edited by Hitesh Raghuvanshi

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Fiona Neill
  • Thanks @hraghuvanshi! Just a couple review comments from myself, over to you :ping_pong:

  • added 1 commit

    • ac2f2371 - Applying suggestions as per API style guide.

    Compare with previous version

  • added 1 commit

    • 5d3d7609 - Suggestion for introducing version history

    Compare with previous version

  • added 2 commits

    • 2ca144ee - Applying suggestions as per API style guide
    • 3d6bb17f - Suggestion for introducing version history

    Compare with previous version

  • added 1 commit

    Compare with previous version

  • added 1 commit

    Compare with previous version

  • added 1 commit

    Compare with previous version

  • Hitesh Raghuvanshi resolved all threads

    resolved all threads

  • added 1 commit

    Compare with previous version

  • Hitesh Raghuvanshi added 245 commits

    added 245 commits

    Compare with previous version

  • Fiona Neill removed review request for @fneill

    removed review request for @fneill

  • Hitesh Raghuvanshi added 853 commits

    added 853 commits

    Compare with previous version

  • Hitesh Raghuvanshi changed milestone to %15.4

    changed milestone to %15.4

  • 1 Warning
    :warning: This merge request includes more than 10 commits. Each commit should meet the following criteria:
    1. Have a well-written commit message.
    2. Has all tests passing when used on its own (e.g. when using git checkout SHA).
    3. Can be reverted on its own without also requiring the revert of commit that came before it.
    4. 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
    :book: 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:

    If needed, you can retry the :repeat: danger-review job that generated this comment.

    Generated by :no_entry_sign: Danger

  • Hitesh Raghuvanshi resolved all threads

    resolved all threads

  • added 1 commit

    • 6cb2464b - Bumping milestone version to 15.4

    Compare with previous version

  • Hitesh Raghuvanshi requested review from @fneill

    requested review from @fneill

  • Fiona Neill removed review request for @fneill

    removed review request for @fneill

  • Hitesh Raghuvanshi marked this merge request as ready

    marked this merge request as ready

  • added 1 commit

    • 095d0c5b - Adding suggestion for feature flag

    Compare with previous version

  • Hitesh Raghuvanshi added 712 commits

    added 712 commits

    Compare with previous version

  • added 1 commit

    Compare with previous version

  • Hitesh Raghuvanshi requested review from @eread

    requested review from @eread

  • Evan Read
  • Evan Read
  • Evan Read
  • Evan Read removed review request for @eread

    removed review request for @eread

  • added 1 commit

    • b5d95777 - Adding suggestions for rephrasing introduction

    Compare with previous version

  • Hitesh Raghuvanshi added 210 commits

    added 210 commits

    Compare with previous version

  • added 1 commit

    • 7d7940c4 - Adding suggestions for adding release version

    Compare with previous version

  • Evan Read requested review from @eread

    requested review from @eread

  • Evan Read resolved all threads

    resolved all threads

  • Evan Read approved this merge request

    approved this merge request

  • Evan Read enabled an automatic merge when the pipeline for c9819dd4 succeeds

    enabled an automatic merge when the pipeline for c9819dd4 succeeds

  • merged

  • Evan Read mentioned in commit a9e63e7e

    mentioned in commit a9e63e7e

  • Evan Read mentioned in merge request !96839 (merged)

    mentioned in merge request !96839 (merged)

  • Evan Read resolved all threads

    resolved all threads

  • Hitesh Raghuvanshi resolved all threads

    resolved all threads

  • added workflowstaging label and removed workflowcanary label

  • Please register or sign in to reply
    Loading