Skip to content

Blur out example username belonging to a real user#42796

Merged
Sharra-writes merged 2 commits intogithub:mainfrom
CourteousCoder:enhancement/blur-example-username-that-belongs-to-real-user
Feb 6, 2026
Merged

Blur out example username belonging to a real user#42796
Sharra-writes merged 2 commits intogithub:mainfrom
CourteousCoder:enhancement/blur-example-username-that-belongs-to-real-user

Conversation

@CourteousCoder
Copy link
Contributor

@CourteousCoder CourteousCoder commented Feb 6, 2026

In list-of-members-selected-bulk.png, blur out the username jsmith of example member "John Smith".

Why:

  • That username belongs to a real GitHub user who, as of this writing, appears to be an active user.
  • Obscuring the username does not detract from the helpfulness of the screenshot in its context. In each of its uses, the purpose of the screenshot is to demonstrate how to perform bulk actions on members of a GitHub Organization.

Closes: #42795

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

Just the one image. I downloaded the PNG currently being used, opened it up in GIMP, and just added a blurring slight mosaic effect over the text to obscure the username. Then I replaced the old image. You can see the before- and after-images in the diff of this PR.

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.

In `list-of-members-selected-bulk.png`, blur out the username `jsmith` of example member "John Smith" because that username belongs to [a real user](https://github.com/jsmith)
@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 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.

This pull request contains code changes, so we will not generate a table of review links.

🤖 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 Feb 6, 2026
@Sharra-writes
Copy link
Contributor

@CourteousCoder This looks like a reasonable change to me, and definitely the simplest option, so I'll take it.

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

github-actions bot commented Feb 6, 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

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.

Someone's real username is being used as an example

2 participants