Skip to content

[Docs] Document team deletion behavior and resource handling#1089

Open
PARTH-TUSSLE wants to merge 1 commit into
layer5io:masterfrom
PARTH-TUSSLE:docs/team-deletion-behavior-1086
Open

[Docs] Document team deletion behavior and resource handling#1089
PARTH-TUSSLE wants to merge 1 commit into
layer5io:masterfrom
PARTH-TUSSLE:docs/team-deletion-behavior-1086

Conversation

@PARTH-TUSSLE
Copy link
Copy Markdown
Contributor

@PARTH-TUSSLE PARTH-TUSSLE commented Jun 7, 2026

Notes for Reviewers

Added documentation describing team deletion behavior, including its impact on memberships, ownership, user accounts, and associated resources.

Preview for the fix :-

{012063C3-9910-4339-8949-C4C0F50CE7B0}

This PR fixes #1086

Signed commits

  • [✅] Yes, I signed my commits.

Signed-off-by: PARTH-TUSSLE <parthgartan26feb@gmail.com>
@welcome
Copy link
Copy Markdown

welcome Bot commented Jun 7, 2026

Yay, your first pull request! 👍 A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Community Welcome Guide and sure to join the community Slack.
Be sure to double-check that you have signed your commits. Here are instructions for making signing an implicit activity while peforming a commit.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a new "Delete a Team" section to the documentation, detailing the effects of team deletion with an example. The reviewer suggested removing a redundant alert box that repeats information already covered in the bullet points and introduction to improve readability.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment on lines +69 to +72

{{< alert type="info" title="Team Deletion" >}}
Deleting a team removes team memberships and ownership, but does not delete user accounts or associated resources.
{{< /alert >}}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This alert box is highly redundant because it repeats the exact same information already detailed in the bullet points above (lines 64-68) and the introductory paragraph (line 60). Removing it simplifies the section and improves readability.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 7, 2026

🚀 Preview deployment: https://layer5io.github.io/docs/pr-preview/pr-1089/

Note: Preview may take a moment (GitHub Pages deployment in progress). Please wait and refresh. Track deployment here

@Bhumikagarggg
Copy link
Copy Markdown
Contributor

@PARTH-TUSSLE Thank you for your contribution! Let's discuss this during the website call tomorrow at 5:30 PM IST | 7 AM CST Add it as an agenda item to the meeting minutes, if you would 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document team deletion behavior and associated resource handling

2 participants