Skip to content

Conversation

@jsoref
Copy link
Contributor

@jsoref jsoref commented Feb 8, 2026

Why:

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.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Feb 8, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Feb 8, 2026

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
account-and-profile/how-tos/organization-membership/publicizing-or-hiding-organization-membership.md fpt
ghec
ghes@ 3.19 3.18 3.17 3.16 3.15 3.14
fpt
ghec
ghes@ 3.19 3.18 3.17 3.16 3.15 3.14

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

🤖 This comment is automatically generated.

@Sharra-writes
Copy link
Contributor

@jsoref Thanks! I'll get this added to the merge queue!

@Sharra-writes Sharra-writes added this pull request to the merge queue Feb 9, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Feb 9, 2026
@jsoref
Copy link
Contributor Author

jsoref commented Feb 9, 2026

@Sharra-writes the outage kicked this out of the merge queue?

@Sharra-writes
Copy link
Contributor

@jsoref I think so. Sometimes the checks also don't like edits to frontmatter in this repo, but I don't think it's that since everything passed earlier and it says something about a 500 error.

@jsoref
Copy link
Contributor Author

jsoref commented Feb 9, 2026

Can you requeue it or something? (or is it best to just wait for the outage to go away and then requeue it?)

@Sharra-writes
Copy link
Contributor

I'm running the test again to see if it works, and if it still doesn't I'll wait until the outage is over and try again.

@Sharra-writes Sharra-writes added this pull request to the merge queue Feb 9, 2026
Merged via the queue into github:main with commit 67652a5 Feb 9, 2026
39 of 40 checks passed
@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues

@jsoref jsoref deleted the issue-42696 branch February 9, 2026 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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.

Publicizing or hiding organization membership doesn't mention that sometimes you can't

2 participants