Skip to content

Commit f38780a

Browse files
wrslatzwrslatz
authored
Merge branch 'main' into gha-hardening-pull-request-target
2 parents 9bde44a + 16fcab0 commit f38780a

File tree

458 files changed

+36456
-4528
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

458 files changed

+36456
-4528
lines changed

‎.github/workflows/changelog-prompt.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ jobs:
5555
" - Did this PR add noteworthy changes to the GitHub docs? If so, you might want to publicize this by adding an entry to " +
5656
"the [Docs changelog](https://github.com/github/docs-internal/blob/main/CHANGELOG.md).\n\n" +
5757
"To do this, type `/changelog` in a new comment on this PR and complete the fields.\n\n" +
58-
"A message will be posted to the **#docs-changelog** channel and a PR will be raised to update the [CHANGELOG.md](/CHANGELOG.md) file.";
58+
"A message will be posted to the **#docs-changelog** channel and a PR will be raised to update the [CHANGELOG.md](https://github.com/github/docs-internal/blob/main/CHANGELOG.md) file.";
5959
6060
// Post the comment
6161
await github.rest.issues.createComment({

‎.github/workflows/headless-tests.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,9 @@ jobs:
5757
- name: Run Playwright tests
5858
env:
5959
PLAYWRIGHT_WORKERS: ${{ fromJSON('[1, 4]')[github.repository == 'github/docs-internal'] }}
60+
# workaround for https://github.com/nodejs/node/issues/59364 as of 22.18.0
61+
NODE_OPTIONS: '--no-experimental-strip-types'
62+
6063
# Run playwright rendering tests and a11y tests (axe scans) as distinct checks
6164
# so that we can run them without blocking merges until we can be confident
6265
# results for a11y tests are meaningul and scenarios we're testing are correct.

‎.github/workflows/local-dev.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,8 @@ jobs:
5050
# by default failures are marked as "flaky" instead of "failed".
5151
PLAYWRIGHT_RETRIES: 0
5252
TEST_EARLY_ACCESS: ${{ github.repository == 'github/docs-internal' }}
53+
# workaround for https://github.com/nodejs/node/issues/59364 as of 22.18.0
54+
NODE_OPTIONS: '--no-experimental-strip-types'
5355
run: npm run playwright-test -- playwright-local-dev
5456

5557
- name: Start server in the background

‎CHANGELOG.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,21 @@
11
# Docs changelog
22

3+
**15 August 2025**
4+
5+
When interacting with the GitHub MCP server for a public repository, push protection blocks secrets from appearing in AI-generated responses and also prevents secrets from being included in any actions you perform, such as creating an issue.
6+
7+
See [Working with push protection and the GitHub MCP server](https://docs.github.com/en/code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-and-the-github-mcp-server).
8+
9+
<hr>
10+
11+
**12 August 2025**
12+
13+
OpenAI GPT-5 is now available in public preview for GitHub Copilot. GPT-5 is slowly rolling out to all paid Copilot plans and you will be able to access the model in GitHub Copilot Chat on github.com and Visual Studio Code (Agent, Ask, and Edit modes).
14+
15+
See [Supported AI models in Copilot](https://docs.github.com/en/copilot/reference/ai-models/supported-models).
16+
17+
<hr>
18+
319
**12 August 2025**
420

521
We’ve updated the documentation for Copilot repository custom instructions to go with the release that now brings this feature to the Eclipse IDE.

‎Dockerfile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ FROM ghcr.io/github/gh-base-image/gh-base-noble:20250805-204228-g50c20871f AS ba
1818
# Must run as root
1919
RUN apt-get -qq update && apt-get -qq install --no-install-recommends curl git \
2020
&& curl -sL https://deb.nodesource.com/setup_22.x | bash - \
21-
&& apt-get install -y nodejs=22.17.0-1nodesource1 \
21+
&& apt-get install -y nodejs \
2222
&& node --version
2323

2424
# Create the node user and home directory

‎assets/images/help/copilot/enterprise-premium-request-budget.png

-66.3 KB
Binary file not shown.

‎content/account-and-profile/concepts/contributions-visible-on-your-profile.md

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
title: Contributions visible on your profile
3+
intro: 'Your profile shows off your pinned repositories, Achievements, and a graph of your repository contributions over the past year.'
4+
versions:
5+
fpt: '*'
6+
ghes: '*'
7+
ghec: '*'
8+
topics:
9+
- Profiles
10+
shortTitle: Contributions on your profile
11+
---
12+
13+
Your contribution graph and Achievements show activity from public repositories. You can choose to show activity from both public and private repositories, with specific details of your activity in private repositories anonymized. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile).
14+
15+
{% data reusables.profile.contribution-graph-commits %}
16+
17+
## Popular repositories
18+
19+
This section displays your repositories with the most watchers. Once you [pin repositories to your profile](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile), this section will change to "Pinned."
20+
21+
## Pinned
22+
23+
This section displays up to six public repositories or gists. Important details are listed for each of the items you've chosen to feature. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile).
24+
25+
![Screenshot of the "Pinned repositories" section of a user's profile page.](/assets/images/help/profile/profile-pinned-repositories.png)
26+
27+
## Contributions calendar
28+
29+
Your contributions calendar shows a visual overview of your contribution activity.
30+
31+
![Screenshot of the contributions graph on a user profile.](/assets/images/help/profile/contributions-graph.png)
32+
33+
## Activity overview
34+
35+
{% data reusables.profile.activity-overview-summary %} For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-an-overview-of-your-activity-on-your-profile).
36+
37+
![Screenshot of the activity overview section of a user profile.](/assets/images/help/profile/activity-overview-section.png)
38+
39+
The organizations featured in the activity overview are prioritized according to how active you are in the organization. If you @mention an organization in your profile bio, and you’re an organization member, then that organization is prioritized first in the activity overview. For more information, see [AUTOTITLE](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#mentioning-people-and-teams) or [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile).
40+
41+
## Contribution activity
42+
43+
The contribution activity section includes a detailed timeline of your work, including commits you've made or co-authored, pull requests you've proposed, and issues you've opened.
44+
45+
Important moments, like the date you joined an organization, proposed your first pull request, or opened a high-profile issue, are highlighted in your contribution activity.
46+
47+
If you can't see certain events in your timeline, check to make sure you still have access to the organization or repository where the event happened.
48+
49+
## Next steps
50+
51+
To learn the different ways to view your contributions, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile).
52+
53+
To learn what counts as a contribution, see [AUTOTITLE](/account-and-profile/reference/why-are-my-contributions-not-showing-up-on-my-profile#what-counts-as-a-contribution)

‎content/account-and-profile/concepts/email-addresses.md

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
---
2+
title: Email addresses
3+
intro: 'Learn about the different types of email addresses you can associate with your {% data variables.product.github %} account—primary, backup, commit, and noreply—and how each type is used for account management, security, and commit attribution.'
4+
versions:
5+
fpt: '*'
6+
ghes: '*'
7+
ghec: '*'
8+
topics:
9+
- Accounts
10+
- Fundamentals
11+
- Profile
12+
shortTitle: Email addresses
13+
---
14+
15+
## Adding an email address to your {% data variables.product.github %} account
16+
17+
{% data variables.product.github %} allows you to add as many email addresses to your account as you like. For more information, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account).
18+
19+
If you set an email address in your local Git configuration, you will need to add it to your account settings in order to connect your commits to your account. For more information about your email address and commits, see [Commit email addresses](#commit-email-addresses) below.
20+
21+
## Changing your primary email address
22+
23+
You can change the email address associated with your personal account at any time. You cannot change your primary email address to an email that is already set to be your backup email address. For more information, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/changing-your-primary-email-address).
24+
25+
## Email verification for personal accounts
26+
27+
You can verify your email address after signing up for a new account, or when you add a new email address. If an email address is undeliverable or bouncing, it will be unverified.
28+
29+
Having an unverified email address does not affect most actions you can take on {% data variables.product.prodname_dotcom %}. However, we **recommend email verification** to prevent potential exploitation of third-party {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} which may not have followed our best practices around secure authentication methods for apps.
30+
31+
For more information, see [AUTOTITLE](/free-pro-team@latest/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/verifying-your-email-address).
32+
33+
## Email verification for {% data variables.enterprise.prodname_managed_users %}
34+
35+
For Enterprise Managed Users (EMUs), email addresses are no longer automatically verified. This prevents unauthorized access and potential data leaks from third-party {% data variables.product.prodname_github_apps %} and OAuth applications that rely on email addresses as a primary identifier.
36+
37+
Until you verify your email address, your account will use a placeholder email address with your enterprise's shortcode appended for certain operations. For example, the [AUTOTITLE](/rest/users/users) and [AUTOTITLE](/rest/users/emails) will return `email+shortcode@domain.com`. In rare cases, you may find that your company's email provider does not handle the placeholder email correctly, or that the placeholder prevents you from accessing some third-party {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}.
38+
39+
Once you verify an email with a {% data variables.enterprise.prodname_managed_user %}, you won't be able to use the email to sign up for a personal account on {% data variables.product.prodname_dotcom_the_website %}.
40+
41+
>[!NOTE] If you need to use the same email address for both your {% data variables.enterprise.prodname_managed_user %} and another {% data variables.product.github %} account (for example, for innersource, open source, or other valid use cases), you must sign in to your managed user account and unverify the email in your account settings.
42+
>
43+
> The email will still be linked to your managed user account, so you can continue signing in through your organization's or enterprise's identity provider (IdP). However, because the email is unverified, it may affect your access to third-party applications that identify users based solely on email address.
44+
45+
## Commit email addresses
46+
47+
{% data variables.product.github %} uses your commit email address to associate commits with your account on {% data variables.product.github %}. You can choose the email address that will be associated with the commits you push from the command line as well as web-based Git operations you make.
48+
49+
For web-based Git operations, you can set your commit email address on {% data variables.product.github %}. For commits you push from the command line, you can set your commit email address in Git.
50+
51+
{% ifversion fpt or ghec %}Any commits you made prior to changing your commit email address are still associated with your previous email address.{% else %}After changing your commit email address on {% data variables.product.github %}, the new email address will be visible in all of your future web-based Git operations by default. Any commits you made prior to changing your commit email address are still associated with your previous email address.{% endif %}
52+
53+
{% ifversion fpt or ghec %}To use your `noreply` email address for commits you push from the command line, use that email address when you set your commit email address in Git. To use your `noreply` address for web-based Git operations, set your commit email address on GitHub and choose to **Keep my email address private**.
54+
55+
You can also choose to block commits you push from the command line that expose your personal email address. For more information, see [AUTOTITLE](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address).{% endif %}
56+
57+
To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.product.github %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}.
58+
59+
For more information, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address).
60+
61+
## Next steps
62+
63+
* For how-to procedures on managing your email preferences, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences).
64+
* For email address reference information, see [AUTOTITLE](/account-and-profile/reference/email-addresses-reference).

‎content/account-and-profile/concepts/index.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Concepts for account and profile
33
shortTitle: Concepts
4-
intro: 'Learn the core concepts that you''ll need to understand your {% data variables.product.github %} account and profile.'
4+
intro: Learn the core concepts that you'll need to understand your {% data variables.product.github %} account and profile.
55
versions:
66
fpt: '*'
77
ghes: '*'
@@ -11,9 +11,11 @@ topics:
1111
- Profiles
1212
children:
1313
- /about-your-profile
14-
- /viewing-contributions-on-your-profile
14+
- /contributions-visible-on-your-profile
1515
- /about-your-organizations-profile
1616
- /about-organization-membership
1717
- /changing-your-github-username
18+
- /email-addresses
1819
- /scheduled-reminders
20+
- /personal-repository-access-and-collaboration
1921
---

‎content/account-and-profile/concepts/personal-repository-access-and-collaboration.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
title: Personal repository access and collaboration
3+
intro: 'Learn how to manage access and collaboration for repositories you own with your personal account on {% data variables.product.github %}.'
4+
versions:
5+
fpt: '*'
6+
ghes: '*'
7+
ghec: '*'
8+
topics:
9+
- Accounts
10+
- Repositories
11+
- Privacy
12+
- Open Source
13+
shortTitle: Access to repositories
14+
---
15+
16+
## About collaboration in a personal repository
17+
18+
You can collaborate with others on repositories you own by inviting them as collaborators. Collaborators have access to contribute to your code and manage issues and pull requests.
19+
20+
{% ifversion ghec %}
21+
22+
If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %}
23+
24+
{% endif %}
25+
26+
To add a collaborator, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository).
27+
28+
{% ifversion fpt or ghec %}
29+
30+
{% data reusables.repositories.private_forks_inherit_permissions %}
31+
32+
## About successors
33+
34+
We recommend inviting another {% data variables.product.company_short %} user to be your successor, to manage your user owned repositories if you cannot. As a successor, they will have permission to:
35+
36+
* Archive your public repositories.
37+
* Transfer your public repositories to their own user owned account.
38+
* Transfer your public repositories to an organization where they can create repositories.
39+
40+
Successors cannot log into your account.
41+
42+
An appointed successor can manage your public repositories after presenting a death certificate then waiting for 7 days or presenting an obituary then waiting for 21 days. For more information, see [AUTOTITLE](/free-pro-team@latest/site-policy/other-site-policies/github-deceased-user-policy).
43+
44+
To request access to manage repositories as a successor, please contact us through the {% data variables.contact.contact_support_portal %}.
45+
46+
For more information, see [AUTOTITLE](/account-and-profile/how-tos/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories).
47+
48+
{% endif %}

0 commit comments

Comments
 (0)