Skip to content

Commit 67dc88c

Browse files
authored
Merge branch 'main' into patch-2
2 parents b581ada + 12c8a81 commit 67dc88c

File tree

455 files changed

+194822
-9302
lines changed

Some content is hidden

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

455 files changed

+194822
-9302
lines changed
17.2 KB
Loading
129 KB
Loading
127 KB
Loading
Binary file not shown.
71.5 KB
Loading

content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ The following SAML attributes are available for {% data variables.product.produc
8080
| `NameID` | Yes | A persistent user identifier. Any persistent name identifier format may be used. {% ifversion ghec %}If you use an enterprise with {% data variables.product.prodname_emus %}, {% endif %}{% data variables.product.product_name %} will normalize the `NameID` element to use as a username unless one of the alternative assertions is provided. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." |
8181
| `SessionNotOnOrAfter` | No | The date that {% data variables.product.product_name %} invalidates the associated session. After invalidation, the person must authenticate once again to access {% ifversion ghec or ghae %}your enterprise's resources{% elsif ghes %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Session duration and timeout](#session-duration-and-timeout)." |
8282
{%- ifversion ghes or ghae %}
83-
| `administrator` | No | When the value is `true`, {% data variables.product.product_name %} will automatically promote the user to be a {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %}. Any other value or a non-existent value will demote the account and remove administrative access. |
83+
| `administrator` | No | When the value is `true`, {% data variables.product.product_name %} will automatically promote the user to be a {% ifversion ghes %}site administrator{% elsif ghae %}enterprise owner{% endif %}. Setting this attribute to anything but `true` will result in demotion, as long as the value is not blank. Omitting this attribute or leaving the value blank will not change the role of the user. |
8484
| `username` | No | The username for {% data variables.product.product_location %}. |
8585
{%- endif %}
8686
| `full_name` | No | {% ifversion ghec %}If you configure SAML SSO for an enterprise and you use {% data variables.product.prodname_emus %}, the{% else %}The{% endif %} full name of the user to display on the user's profile page. |

content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1337,6 +1337,34 @@ Key | Type | Description
13371337
13381338
{% endif %}
13391339
1340+
{% ifversion ghas-enablement-webhook %}
1341+
1342+
## security_and_analysis
1343+
1344+
Activity related to enabling or disabling code security and analysis features for a repository or organization.
1345+
1346+
### Availability
1347+
1348+
- Repository webhooks
1349+
- Organization webhooks
1350+
- {% data variables.product.prodname_github_apps %} with at least `read-only` access on repositories administration
1351+
1352+
### Webhook payload object
1353+
1354+
Key | Type | Description
1355+
----|------|-------------
1356+
`changes`|`object` | The changes that were made to the code security and analysis features.
1357+
{% data reusables.webhooks.repo_desc %}
1358+
{% data reusables.webhooks.org_desc %}
1359+
{% data reusables.webhooks.app_desc %}
1360+
{% data reusables.webhooks.sender_desc %}
1361+
1362+
### Webhook payload example
1363+
1364+
{{ webhookPayloadsForCurrentVersion.security_and_analysis }}
1365+
1366+
{% endif %}
1367+
13401368
{% ifversion fpt or ghec %}
13411369
## sponsorship
13421370

content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,16 @@ Starring a repository is a simple two-step process.
4141
![Untarring a repository](/assets/images/help/stars/unstarring-a-repository.png)
4242

4343
{% ifversion fpt or ghec %}
44+
45+
## Viewing who has starred a repository
46+
47+
48+
You can view everyone who has starred a public repository or a private repository you have access to.
49+
50+
51+
To view everyone who has starred a repository, add `/stargazers` to the end of the URL of a repository. For example, to view stargazers for the github/docs repository, visit https://github.com/github/docs/stargazers.
52+
53+
4454
## Organizing starred repositories with lists
4555

4656
{% note %}

content/get-started/quickstart/contributing-to-projects.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ gh repo fork <em>repository</em> --clone=true
8282

8383
## Making and pushing changes
8484

85-
Go ahead and make a few changes to the project using your favorite text editor, like [Atom](https://atom.io). You could, for example, change the text in `index.html` to add your GitHub username.
85+
Go ahead and make a few changes to the project using your favorite text editor, like [Visual Studio Code](https://code.visualstudio.com). You could, for example, change the text in `index.html` to add your GitHub username.
8686

8787
When you're ready to submit your changes, stage and commit your changes. `git add .` tells Git that you want to include all of your changes in the next commit. `git commit` takes a snapshot of those changes.
8888

content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md

Lines changed: 23 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -15,17 +15,37 @@ topics:
1515
- Pull requests
1616
shortTitle: Create & delete branches
1717
---
18+
1819
## Creating a branch
20+
You can create a branch in different ways on {% data variables.product.product_name %}.
21+
22+
{% note %}
1923

24+
**Note:** You can only create a branch in a repository to which you have push access.
25+
26+
{% endnote %}
27+
28+
### Creating a branch via the branches overview
2029
{% data reusables.repositories.navigate-to-repo %}
30+
{% data reusables.repositories.navigate-to-branches %}
31+
1. Click **New branch**.
32+
![Screenshot of branches overview page with new branch button emphasized](/assets/images/help/branches/new-branch-button.png)
33+
2. In the dialog box, enter the branch name and optionally change the branch source.
34+
3. Click **Create branch**.
35+
![Screenshot of branch creation modal with create branch button emphasized](/assets/images/help/branches/branch-creation-popup.png)
2136

22-
1. Optionally, if you want to create your new branch from a branch other than the default branch for the repository, click {% octicon "git-branch" aria-label="The branch icon" %} **<em>NUMBER</em> branches** then choose another branch:
23-
![Branches link on overview page](/assets/images/help/branches/branches-link.png)
37+
### Creating a branch using the branch dropdown
38+
{% data reusables.repositories.navigate-to-repo %}
39+
1. Optionally, if you want to create the new branch from a branch other than the default branch of the repository, click {% octicon "git-branch" aria-label="The branch icon" %} **Branches** then choose another branch.
40+
![Branches link on overview page](/assets/images/help/branches/branches-overview-link.png)
2441
1. Click the branch selector menu.
2542
![branch selector menu](/assets/images/help/branch/branch-selection-dropdown.png)
2643
1. Type a unique name for your new branch, then select **Create branch**.
2744
![branch creation text box](/assets/images/help/branch/branch-creation-text-box.png)
28-
45+
{% ifversion fpt or ghec or ghes > 3.4 %}
46+
### Creating a branch for an issue
47+
You can create a branch to work on an issue directly from the issue page and get started right away. For more information, see "[Creating a branch to work on an issue](/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue)".
48+
{% endif %}
2949
## Deleting a branch
3050

3151
{% data reusables.pull_requests.automatically-delete-branches %}

0 commit comments

Comments
 (0)