1
0
mirror of synced 2026-01-06 06:02:35 -05:00

Merge pull request #17269 from github/repo-sync

repo sync
This commit is contained in:
Octomerger Bot
2022-04-21 10:52:40 -07:00
committed by GitHub
6 changed files with 1070 additions and 1010 deletions

View File

@@ -17,5 +17,6 @@ children:
- /personalizing-your-profile
- /managing-your-profile-readme
- /pinning-items-to-your-profile
- /setting-your-profile-to-private
---

View File

@@ -151,7 +151,7 @@ You can disable some of the badges for {% data variables.product.prodname_dotcom
{% data reusables.user-settings.access_settings %}
2. Under "Profile settings", deselect the badge you want you disable.
![Checkbox to no longer display a badge on your profile](/assets/images/help/profile/profile-badge-settings.png)
3. Click **Update preferences**.
{% data reusables.user-settings.update-preferences %}
{% endif %}

View File

@@ -0,0 +1,62 @@
---
title: Setting your profile to private
intro: A private profile displays only limited information, and hides some activity.
versions:
fpt: '*'
topics:
- Profiles
shortTitle: Set profile to private
---
## About private profiles
{% note %}
**Note:** Private profiles are currently in beta and are subject to change.
{% endnote %}
To hide parts of your profile page, you can make your profile private. This also hides your activity in various social features on {% data variables.product.prodname_dotcom_the_website %}. A private profile hides information from all users, and there is currently no option to allow specified users to see your activity.
After making your profile private, you can still view all your information when you visit your own profile.
Private profiles cannot receive sponsorships under [{% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors). To be eligible for {% data variables.product.prodname_sponsors %}, your profile cannot be private.
## Differences between private and public profiles
When your profile is private, the following content is hidden from your profile page:
- Achievements and highlights.
- Activity overview and activity feed.
- Contribution graph.
- Follower and following counts.
- Follow and Sponsor buttons.
- Organization memberships.
- Stars, projects, packages, and sponsoring tabs.
{% note %}
**Note**: When your profile is private, some optional fields are still publicly visible, such as the README, biography, and profile photo.
{% endnote %}
## Changes to reporting on your activities
By making your profile private, you will not remove or hide past activity; this setting only applies to your activity while the private setting is enabled.
When your profile is private, your {% data variables.product.prodname_dotcom_the_website %} activity will not appear in the following locations:
- Activity feeds for other users.
- Discussions leaderboards.
- The [Trending](https://github.com/trending) page.
{% note %}
**Note**: Your activity on public repositories will still be publicly visible to anyone viewing those repositories, and some activity data may still be available through the {% data variables.product.prodname_dotcom %} API.
{% endnote %}
## Changing your profile's privacy settings
{% data reusables.user-settings.access_settings %}
1. Under "Contributions & Activity", select the checkbox next to **Make profile private and hide activity**.
{% data reusables.user-settings.update-preferences %}

View File

@@ -0,0 +1 @@
1. Click **Update preferences**.

File diff suppressed because it is too large Load Diff

View File

@@ -1,6 +1,6 @@
import { statSync } from 'fs'
import fs from 'fs/promises'
import path from 'path'
import { filter as asyncFilter } from 'async'
describe('check for orphan tests', () => {
test('all tests are in sub-directories', async () => {
@@ -11,14 +11,10 @@ describe('check for orphan tests', () => {
// Get a list of files/directories in `/tests`
const testDirectory = await fs.readdir(pathToTests)
// Filter out our exceptions
let filteredList = testDirectory.filter((item) => !EXCEPTIONS.includes(item))
// Don't include directories
filteredList = await asyncFilter(
filteredList,
async (item) => !(await fs.stat(path.join(pathToTests, item))).isDirectory()
)
// Filter out our exceptions and directories
const filteredList = testDirectory
.filter((item) => !EXCEPTIONS.includes(item))
.filter((item) => !statSync(path.join(pathToTests, item)).isDirectory())
expect(filteredList).toHaveLength(0)
})