Merge branch 'main' into main
This commit is contained in:
Matt Pollard
@@ -30,7 +30,7 @@ People who visit your profile see a timeline of your contribution activity, like
|
||||
People who visit your profile can also see the following information.
|
||||
|
||||
- Repositories and gists you own or contribute to. {% ifversion fpt or ghes or ghec %}You can showcase your best work by pinning repositories and gists to your profile. For more information, see "[Pinning items to your profile](/github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile)."{% endif %}
|
||||
- Repositories you've starred{% ifversion fpt or ghec %} and organized into lists.{% endif %} For more information, see "[Saving repositories with stars](/articles/saving-repositories-with-stars/)."
|
||||
- Repositories you've starred{% ifversion fpt or ghec %} and organized into lists{% endif %}. For more information, see "[Saving repositories with stars](/articles/saving-repositories-with-stars/)."
|
||||
- An overview of your activity in organizations, repositories, and teams you're most active in. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."{% ifversion fpt or ghec %}
|
||||
- Badges and Achievements that highlight your activity and show if you use {% data variables.product.prodname_pro %} or participate in programs like the {% data variables.product.prodname_arctic_vault %}, {% data variables.product.prodname_sponsors %}, or the {% data variables.product.company_short %} Developer Program. For more information, see "[Personalizing your profile](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#displaying-badges-on-your-profile)."{% endif %}
|
||||
|
||||
|
||||
@@ -608,7 +608,7 @@ jobs:
|
||||
|
||||
## `secrets` context
|
||||
|
||||
The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions. For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
|
||||
The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions due to security reasons. If you want to pass a secret to a composite action, you need to do it explicitly as an input. For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
|
||||
|
||||
`GITHUB_TOKEN` is a secret that is automatically created for every workflow run, and is always included in the `secrets` context. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
|
||||
|
||||
|
||||
@@ -105,14 +105,6 @@ featuredLinks:
|
||||
- '{% ifversion ghec %}/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks{% endif %}'
|
||||
- /billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise
|
||||
- /admin/enterprise-support/about-github-enterprise-support
|
||||
videos:
|
||||
- title: GitHub in the Enterprise – Maya Ross
|
||||
href: 'https://www.youtube-nocookie.com/embed/1-i39RqaxRs'
|
||||
- title: What's new for GitHub Enterprise – Jarryd McCree
|
||||
href: 'https://www.youtube-nocookie.com/embed/ZZviWZgrqhM'
|
||||
- title: Enforcing information security policy through GitHub Enterprise – Thomas Worley
|
||||
href: 'https://www.youtube-nocookie.com/embed/DCu-ZTT7WTI'
|
||||
videosHeading: GitHub Universe 2021 videos
|
||||
layout: product-landing
|
||||
versions:
|
||||
ghec: '*'
|
||||
|
||||
@@ -49,7 +49,7 @@ If you have {% data variables.product.prodname_github_connect %} enabled for {%
|
||||
|
||||
1. Navigate to `https://HOSTNAME/advisories`.
|
||||
2. Select the security advisory you would like to contribute to.
|
||||
3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on Github.com.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on {% data variables.product.prodname_dotcom_the_website %}.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
4. Edit the advisory, following steps four through six in "[Editing advisories in the GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database)" above.
|
||||
{% endif %}
|
||||
|
||||
@@ -30,11 +30,14 @@ For a submission with a purpose of `Learn`, your repository must have:
|
||||
- A description.
|
||||
- A LEARN.md file to provide step-by-step instructions, with text and/or media, on how you built your project. Ideally, your LEARN.md file will deconstruct your project into small components and provide thorough details of each step, so that other students can code their project by following your instructions.
|
||||
- A README.md file to provide a detailed description of your project.
|
||||
- A License so others are aware of what they can and cannot do with your source code.
|
||||
|
||||
For a submission with a purpose of `Collaborate`, your repository must have:
|
||||
- A description.
|
||||
- A README.md file to provide a detailed description of your project.
|
||||
- A License so others are aware of what they can and cannot do with your source code.
|
||||
- One or more issues for collaborators to work on.
|
||||
- CONTRIBUTING.md file to communicate how to contribute to your project.
|
||||
|
||||
A good repository submission for both `Learn` and `Collaborate` purposes, is a repository that follows community standards. For more information, see "[About community profiles for public repositories](/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories)."
|
||||
|
||||
|
||||
@@ -511,7 +511,7 @@ The response will contain the node ID of the newly created draft issue.
|
||||
```json
|
||||
{
|
||||
"data": {
|
||||
"addProjectV2ItemById": {
|
||||
"addProjectV2DraftIssue": {
|
||||
"projectItem": {
|
||||
"id": "PVTI_lADOANN5s84ACbL0zgBbxFc"
|
||||
}
|
||||
|
||||
@@ -77,8 +77,8 @@ To search for specific events, use the `action` qualifier in your query. Actions
|
||||
| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% ifversion fpt or ghec %}
|
||||
| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae or ghec %}
|
||||
| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
|
||||
| [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
|
||||
| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}
|
||||
| [`repository_secret_scanning_custom_pattern`](#repository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion secret-scanning-audit-log-custom-patterns %}
|
||||
| [`repository_secret_scanning_push_protection`](#repository_secret_scanning_push_protection-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}
|
||||
| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts).{% ifversion fpt or ghec %}
|
||||
| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% ifversion custom-repository-roles %}
|
||||
| [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %}
|
||||
|
||||
@@ -73,7 +73,9 @@ Some of the features listed below are limited to organizations using {% data var
|
||||
| Reopen issues they closed themselves | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
|
||||
| Have an issue assigned to them | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
|
||||
| Send pull requests from forks of the team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
|
||||
| Submit reviews on pull requests | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
|
||||
| [Submit reviews on pull requests](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
|
||||
| [Approve or request changes to a pull request with required reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/approving-a-pull-request-with-required-reviews) | | | **✔️** | **✔️** | **✔️** |
|
||||
| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **✔️** | **✔️** | **✔️** |
|
||||
| View published releases | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %}
|
||||
| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %}
|
||||
| Edit wikis in public repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |
|
||||
@@ -95,8 +97,6 @@ Some of the features listed below are limited to organizations using {% data var
|
||||
| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **✔️** | **✔️** | **✔️** |
|
||||
| [Mark a draft pull request as ready for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** |
|
||||
| [Convert a pull request to a draft](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** |
|
||||
| Submit reviews that affect a pull request's mergeability | | | **✔️** | **✔️** | **✔️** |
|
||||
| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **✔️** | **✔️** | **✔️** |
|
||||
| Create [status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %}
|
||||
| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **✔️** | **✔️** | **✔️** |{% endif %}
|
||||
| Create and edit releases | | | **✔️** | **✔️** | **✔️** |
|
||||
|
||||
@@ -48,14 +48,15 @@ Before you can use Jekyll to test a site, you must:
|
||||
> Server address: http://127.0.0.1:4000/
|
||||
> Server running... press ctrl-c to stop.
|
||||
```
|
||||
{% note %}
|
||||
|
||||
**Note:** If you've installed Ruby 3.0 or later (which you may have if you installed the default version via Homebrew), you might get an error at this step. That's because these versions of Ruby no longer come with `webrick` installed.
|
||||
|
||||
To fix the error, try running `bundle add webrick`, then re-running `bundle exec jekyll serve`.
|
||||
{% endnote %}
|
||||
|
||||
3. To preview your site, in your web browser, navigate to `http://localhost:4000`.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you are using Ruby 3.0 and Jekyll 4.2.x or older, you will need to add the `webrick` gem to your project's Gemfile prior to running `bundle install`.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Updating the {% data variables.product.prodname_pages %} gem
|
||||
|
||||
Jekyll is an active open source project that is updated frequently. If the `github-pages` gem on your computer is out of date with the `github-pages` gem on the {% data variables.product.prodname_pages %} server, your site may look different when built locally than when published on {% data variables.product.product_name %}. To avoid this, regularly update the `github-pages` gem on your computer.
|
||||
|
||||
@@ -289,7 +289,7 @@ In addition, if your account has private repositories, you control the access to
|
||||
- to comply with our legal obligations if we have reason to believe the contents are in violation of the law,
|
||||
- or with your consent.
|
||||
|
||||
Github will provide notice regarding private repository access where not prohibited by law or if in response to a security threat or other risk to security.
|
||||
GitHub will provide notice regarding private repository access where not prohibited by law or if in response to a security threat or other risk to security.
|
||||
|
||||
### Cross-border data transfers
|
||||
GitHub processes personal data both inside and outside of the United States and relies on legal mechanisms such as Standard Contractual Clauses to lawfully transfer data from the European Economic Area, the United Kingdom, and Switzerland to the United States. You may request a copy of the Standard Contractual Clauses using the contact details provided in the section entitled “Contacting GitHub” below.
|
||||
@@ -307,7 +307,7 @@ United States<br>
|
||||
**privacy [at] github [dot] com**<br>
|
||||
|
||||
**If you are outside of North America:**<br>
|
||||
Github Data Protection Officer<br>
|
||||
GitHub Data Protection Officer<br>
|
||||
c/o DP Dock DPO Services GmbH,<br>
|
||||
Attn: GitHub BV, Gut Projensdorf,<br>
|
||||
24161 Altenholz, Germany<br>
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
1. Click **New runner**, then click **{% octicon "mark-github" aria-label="New hosted runner" %} New Github-hosted runner**.
|
||||
1. Click **New runner**, then click **{% octicon "mark-github" aria-label="New hosted runner" %} New {% data variables.product.prodname_dotcom %}-hosted runner**.
|
||||
1. Complete the required details to configure your new runner:
|
||||
|
||||
- **Name**: Enter a name for your new runner. For easier identification, this should indicate its hardware and operating configuration, such as `ubuntu-20.04-16core`.
|
||||
|
||||
Reference in New Issue
Block a user