Skip to content

Revise blocking user guidelines in organization documentation - #46223

Closed
damn-am-star wants to merge 3 commits into
github:repo-syncfrom
damn-am-star:patch-2
Closed

damn-am-star wants to merge 3 commits into
github:repo-syncfrom
damn-am-star:patch-2

Conversation

@damn-am-star

Copy link
Copy Markdown

Updated the markdown file to include blocking user guidelines and organization settings.

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

docs-bot and others added 3 commits October 6, 2026 13:36
Updated the markdown file to include blocking user guidelines and organization settings.
@damn-am-star
damn-am-star changed the base branch from main to repo-sync October 7, 2026 01:29
@docs-bot docs-bot added the invalid This issue/PR is invalid label Oct 7, 2026
@docs-bot

docs-bot commented Oct 7, 2026

Copy link
Copy Markdown
Collaborator

Pull requests must target the main branch. This pull request has been closed as invalid. If you think this is incorrect, please mention this in a corresponding issue.

@docs-bot docs-bot closed this Oct 7, 2026
@github-actions

github-actions Bot commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

invalid This issue/PR is invalid triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants