Delete orphaned reusables (May 18, 2023) (#37156)
This commit is contained in:
Peter Bengtsson
@@ -1 +0,0 @@
|
||||
actions/delete-package-versions@{% ifversion actions-node16-action %}v3{% else %}v2{% endif %}
|
||||
@@ -1 +0,0 @@
|
||||
You need to trigger several workflow runs before checking if the cache is effective. {% data variables.product.prodname_actions_runner_controller %} requires an `Available` PV to be reused for the new runner pod, and a PV becomes `Available` only after some time after the previous runner pod that was using the PV terminated. For more information, see [this discussion](https://github.com/actions/actions-runner-controller/discussions/1605).
|
||||
@@ -1,3 +0,0 @@
|
||||
- Optionally, autoscaling parameters for each pool.
|
||||
- Minimum number of idle runners for the pool
|
||||
- Active timeout: The number of minutes that a runner should remain active in the pool before the pool is reduced to the idle count
|
||||
@@ -1,5 +0,0 @@
|
||||
| vCPUs | Memory | Maximum Concurrency |
|
||||
| :--- | :--- | :--- |
|
||||
| 32 | 128 GB | 1000 jobs |
|
||||
| 64 | 256 GB | 1300 jobs |
|
||||
| 96 | 384 GB | 2200 jobs |
|
||||
@@ -1,7 +0,0 @@
|
||||
| vCPUs | Memory | Maximum Concurrency |
|
||||
| :--- | :--- | :--- |
|
||||
| 8 | 64 GB | 300 jobs |
|
||||
| 16 | 128 GB | 700 jobs |
|
||||
| 32 | 160 GB | 1300 jobs |
|
||||
| 64 | 256 GB | 2000 jobs |
|
||||
| 96 | 384 GB | 4000 jobs |
|
||||
@@ -1,6 +0,0 @@
|
||||
| vCPUs | Memory | Maximum job throughput |
|
||||
| :--- | :--- | :--- |
|
||||
| 4 | 32 GB | Demo or light testing |
|
||||
| 8 | 64 GB | 25 jobs |
|
||||
| 16 | 160 GB | 35 jobs |
|
||||
| 32 | 256 GB | 100 jobs |
|
||||
@@ -1,2 +0,0 @@
|
||||
1. In the runner section of the settings page, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} next to the runner group you'd like to configure, then click **Edit name and [organization|repository] access**.
|
||||
1. Modify your policy options, or change the runner group name.
|
||||
@@ -1 +0,0 @@
|
||||
1. Click the "Self-hosted runners" tab, and locate the list of runners.
|
||||
@@ -1,6 +0,0 @@
|
||||
To add OIDC integration to your cloud deployment workflows, you will need to add the following code changes:
|
||||
|
||||
- Grant permission to fetch the token from the {% data variables.product.prodname_dotcom %} OIDC provider:
|
||||
- The workflow needs a `permissions` setting with a defined `id-token` value. This lets you fetch the OIDC token from every job in the workflow. If you only need to fetch an OIDC token for a single job, then this permission can be set within that job.
|
||||
- Request the JSON Web Token (JWT) from the {% data variables.product.prodname_dotcom %} OIDC provider, and present it to your cloud provider to receive an access token:
|
||||
- You could use the Actions toolkit to fetch the tokens in your job, or you can use the official action created by your cloud provider to fetch the JWT and receive the access token from the cloud.
|
||||
@@ -1 +0,0 @@
|
||||
To create secrets using the REST API, you must have write access to the repository or admin access to the organization. For more information, see "[AUTOTITLE](/rest/actions#secrets)."
|
||||
@@ -1,3 +0,0 @@
|
||||
1. Assign a policy for organization access.
|
||||
|
||||
You can configure a runner group to be accessible to a specific list of organizations, or all organizations in the enterprise.{% ifversion ghec or ghes %} By default, only private repositories can access runners in a runner group, but you can override this. This setting can't be overridden if configuring an organization's runner group that was shared by an enterprise.{% endif %}
|
||||
@@ -1 +0,0 @@
|
||||
1. Locate the list of runners under "Runners".
|
||||
@@ -1 +0,0 @@
|
||||
1. In the left sidebar, under "Actions", click **Runners**.
|
||||
@@ -1,5 +0,0 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** The ability to add resource links to blocked push messages is currently in public beta and subject to change.
|
||||
|
||||
{% endnote %}
|
||||
@@ -1 +0,0 @@
|
||||
To keep user access tokens more secure, you can use access tokens that will expire after 8 hours, and a refresh token that can be exchanged for a new access token. For more information, see "[AUTOTITLE](/apps/creating-github-apps/authenticating-with-a-github-app/refreshing-user-access-tokens)."
|
||||
@@ -1 +0,0 @@
|
||||
{% ifversion fpt or ghec %}If you are using your OAuth App with GitHub Actions and want to modify workflow files, your OAuth token must have the `workflow` scope and the user must have owner or write permission to the repository that contains the workflow file. For more information, see "[AUTOTITLE](/apps/oauth-apps/building-oauth-apps/scopes-for-oauth-apps#available-scopes)."{% endif %}
|
||||
@@ -1,5 +0,0 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** The Checks API only looks for pushes in the repository where the check suite or check run were created. Pushes to a branch in a forked repository are not detected and return an empty `pull_requests` array and a `null` value for `head_branch`.
|
||||
|
||||
{% endnote %}
|
||||
@@ -1,13 +0,0 @@
|
||||
After you export the log as JSON or CSV, you'll see the following keys and values in the resulting file.
|
||||
|
||||
| Key | Example value
|
||||
|------------|-------------
|
||||
| `@timestamp` | 1429548104000
|
||||
| `actor` | octocat
|
||||
| `action` | git.clone
|
||||
| `org` | octo-org
|
||||
| `business` | avocado-corp
|
||||
| `repo` | octo-org/documentation
|
||||
| `repository_public` | false
|
||||
| `user` | codertocat
|
||||
| `protocol_name` | http
|
||||
@@ -1,3 +0,0 @@
|
||||
You can prevent students from changing files that contain tests for autograding, or other important files in the assignment repository.
|
||||
|
||||
Under "Protected file paths", type relative paths within the repository to protect.
|
||||
@@ -1 +0,0 @@
|
||||
To get started, see "[AUTOTITLE](/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github)."
|
||||
@@ -1 +0,0 @@
|
||||
You can create a default codespace configuration for your repository that determines the environment of every new codespace anyone creates for that repository. The configuration defines a development container that can include frameworks, tools, extensions, and port forwarding.
|
||||
@@ -1 +0,0 @@
|
||||
Your `dotfiles` personalization is applied before a repository's default codespace configuration.
|
||||
@@ -1 +0,0 @@
|
||||
Each codespace is associated with a specific branch of a repository.
|
||||
@@ -1 +0,0 @@
|
||||
1. To accept a suggestion from the new tab, above the suggestion you want to accept, click **Accept solution**.
|
||||
@@ -1 +0,0 @@
|
||||
1. If {% data variables.product.prodname_copilot %} offers a suggestion you want to accept, press <kbd>Tab</kbd>.
|
||||
@@ -1 +0,0 @@
|
||||
1. Alternatively, to reject all suggestions, close the suggestions tab.
|
||||
@@ -1 +0,0 @@
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} cannot use {% data variables.product.prodname_copilot %}.
|
||||
@@ -1,8 +0,0 @@
|
||||
## Enabling or disabling {% data variables.product.prodname_copilot %}
|
||||
|
||||
You can enable or disable {% data variables.product.prodname_copilot %} from within JetBrains. The {% data variables.product.prodname_copilot %} status icon in the bottom panel of the JetBrains window indicates whether {% data variables.product.prodname_copilot %} is enabled or disabled. When enabled, the icon is highlighted. When disabled, the icon is grayed out.
|
||||
|
||||
1. To enable or disable {% data variables.product.prodname_copilot %}, click the status icon in the bottom panel of the JetBrains window.
|
||||
|
||||
2. If you are disabling {% data variables.product.prodname_copilot %}, JetBrains will ask whether you want to disable the feature globally, or for the language of the file you are currently editing. To disable globally, click **Disable Completions**. Alternatively, click the button to disable completions for the language of the file you are currently editing.
|
||||
|
||||
@@ -1,4 +0,0 @@
|
||||
## Further reading
|
||||
|
||||
- [{% data variables.product.prodname_copilot %}](https://copilot.github.com/)
|
||||
- [About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot-for-individuals)
|
||||
@@ -1 +0,0 @@
|
||||
1. Alternatively, to reject all suggestions, press <kbd>Esc</kbd>.
|
||||
@@ -1,5 +0,0 @@
|
||||
1. In the C# file, type the following function header.
|
||||
|
||||
```csharp{:copy}
|
||||
function calculateDaysBetweenDates(begin, end) {
|
||||
```
|
||||
@@ -1 +0,0 @@
|
||||
- On Windows or Linux, press <kbd>Alt</kbd>+<kbd>]</kbd> for the next suggestion, or <kbd>Alt</kbd>+<kbd>[</kbd> for the previous suggestion.
|
||||
@@ -1 +0,0 @@
|
||||
1. Copy the email address you'd like to use in your local Git configuration.
|
||||
@@ -1 +0,0 @@
|
||||
1. Return to {% data variables.product.prodname_desktop %}.
|
||||
@@ -1 +0,0 @@
|
||||
1. Sign in to {% data variables.product.prodname_dotcom %} or {% data variables.product.prodname_enterprise %}.
|
||||
@@ -1 +0,0 @@
|
||||
1. In the list of branches, click the branch you want to switch to.
|
||||
@@ -1 +0,0 @@
|
||||
1. Confirm the change by clicking **Remove credit card** or **Remove PayPal account**.
|
||||
@@ -1,5 +0,0 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** The Dormant Users report is currently in beta and subject to change. During the beta, ongoing improvements to the report download feature may limit its availability.
|
||||
|
||||
{% endnote %}
|
||||
@@ -1 +0,0 @@
|
||||
You will receive a monthly bill for {% data variables.product.prodname_ghe_managed %}, with charges that are calculated per licensed user per day.
|
||||
@@ -1,2 +0,0 @@
|
||||
AWS_ACCESS_KEY | The access key for your AWS S3 bucket
|
||||
AWS_SECRET_KEY | The secret key for your AWS S3 bucket
|
||||
@@ -1 +0,0 @@
|
||||
AWS-REGION | The AWS region where your S3 bucket is located
|
||||
@@ -1 +0,0 @@
|
||||
AWS-SESSION-TOKEN | The AWS session token, if you're using temporary credentials (see [Using temporary credentials with AWS resources](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_use-resources.html) in the AWS documentation)
|
||||
@@ -1 +0,0 @@
|
||||
For more information about how you can try {% data variables.product.prodname_enterprise %} for free, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)" and "[Setting up a trial of {% data variables.product.prodname_ghe_server %}]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)."
|
||||
@@ -1,5 +0,0 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** Features such as {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, {% data variables.product.prodname_mobile %} and {% data variables.product.prodname_GH_advanced_security %} are available on {% data variables.product.prodname_ghe_server %} 3.0 or higher. We highly recommend upgrading to 3.0 or later releases to take advantage of critical security updates, bug fixes and feature enhancements.
|
||||
|
||||
{% endnote %}
|
||||
@@ -1,3 +0,0 @@
|
||||
1. Apply the new configuration. {% data reusables.enterprise.use-a-multiplexer %}
|
||||
|
||||
ghe-cluster-config-apply
|
||||
@@ -1 +0,0 @@
|
||||
The cluster configuration file lists each node under a <code>[cluster "<em>HOSTNAME</em>"]</code> heading.
|
||||
@@ -1,5 +0,0 @@
|
||||
1. After the configuration run finishes, {% data variables.product.prodname_ghe_server %} displays the following message.
|
||||
|
||||
```shell
|
||||
Finished cluster configuration
|
||||
```
|
||||
@@ -1 +0,0 @@
|
||||
The order of the key-value pairs doesn't matter.
|
||||
@@ -1,3 +0,0 @@
|
||||
1. Open the cluster configuration file at _/data/user/common/cluster.conf_ in a text editor. For example, you can use Vim.
|
||||
|
||||
sudo vim /data/user/common/cluster.conf
|
||||
@@ -1,5 +0,0 @@
|
||||
{% note %}
|
||||
|
||||
**Note**: The 127.0.0.1 entry is required to be the first entry in the list. Do not remove the 127.0.0.1 entry, add another entry above the 127.0.0.1 entry, or use options that affect the ordering of entries, such as "options rotate".
|
||||
|
||||
{% endnote %}
|
||||
@@ -1 +0,0 @@
|
||||
If you can't see **{% data variables.product.prodname_advanced_security %}** in the sidebar, it means that your license doesn't include support for {% data variables.product.prodname_advanced_security %} features, including {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}. The {% data variables.product.prodname_advanced_security %} license gives you and your users access to features that help you make your repositories and code more secure. For more information, see "[AUTOTITLE](/get-started/learning-about-github/about-github-advanced-security)" or contact {% data variables.contact.contact_enterprise_sales %}.
|
||||
@@ -1 +0,0 @@
|
||||
A team that's [synced to an LDAP group](/admin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap#enabling-ldap-sync) is indicated with a special LDAP badge. The member list for an LDAP synced team can only be managed from the LDAP group it's mapped to.
|
||||
@@ -1,2 +0,0 @@
|
||||
1. On {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% else %}{% data variables.product.prodname_ghe_managed %}{% endif %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
|
||||
|
||||
@@ -1,5 +0,0 @@
|
||||
{% tip %}
|
||||
|
||||
**Tip:** If you regularly push large files to {% data variables.location.product_location %}, consider using {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[AUTOTITLE](/repositories/working-with-files/managing-large-files)."
|
||||
|
||||
{% endtip %}
|
||||
@@ -1 +0,0 @@
|
||||
You can request publication with or without verification. Requesting publication without verification allows you to launch a free version of your app quickly. If you then request publication with verification, your listing will be updated to include the marketplace badge and any paid pricing plans when you complete verification and financial onboarding.
|
||||
@@ -1 +0,0 @@
|
||||
Unverified apps are only offered with free plans. To list paid plans, you must submit a verified app.
|
||||
@@ -1 +0,0 @@
|
||||
You automatically watch all repositories that you create and are owned by your personal account. You can also choose to automatically watch all repositories that you have push access to, except forks. You can watch any other repository manually.
|
||||
@@ -1 +0,0 @@
|
||||
1. In the left sidebar, to view your saved notifications, click **Saved for later**.
|
||||
@@ -1 +0,0 @@
|
||||
You can choose the delivery method and frequency of notifications about {% data variables.product.prodname_dependabot_alerts %} on repositories that you are watching or where you have subscribed to notifications for security alerts.
|
||||
@@ -1 +0,0 @@
|
||||
1. In the left sidebar, click **Repository labels**.
|
||||
@@ -1 +0,0 @@
|
||||
Team discussions are only available on team pages in organizations. For more information, see "[AUTOTITLE](/organizations/collaborating-with-your-team/about-team-discussions)."
|
||||
@@ -1,15 +0,0 @@
|
||||
Members with team maintainer permissions can:
|
||||
|
||||
- [Change the team's name and description](/organizations/organizing-members-into-teams/renaming-a-team)
|
||||
- [Change the team's visibility](/organizations/organizing-members-into-teams/changing-team-visibility)
|
||||
- [Request to add a child team](/organizations/organizing-members-into-teams/requesting-to-add-a-child-team)
|
||||
- [Request to add or change a parent team](/organizations/organizing-members-into-teams/requesting-to-add-or-change-a-parent-team)
|
||||
- [Set the team profile picture](/organizations/organizing-members-into-teams/setting-your-teams-profile-picture){% ifversion team-discussions %}
|
||||
- [Edit team discussions](/communities/moderating-comments-and-conversations/managing-disruptive-comments#editing-a-comment)
|
||||
- [Delete team discussions](/communities/moderating-comments-and-conversations/managing-disruptive-comments#deleting-a-comment){% endif %}
|
||||
- [Add organization members to the team](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)
|
||||
- [Remove organization members from the team](/organizations/organizing-members-into-teams/removing-organization-members-from-a-team)
|
||||
- [Promote an existing team member to team maintainer](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)
|
||||
- Remove the team's access to repositories
|
||||
- [Manage code review settings for the team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team){% ifversion fpt or ghec %}
|
||||
- [Manage scheduled reminders for pull requests](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %}
|
||||
@@ -1 +0,0 @@
|
||||
1. On the left side of the team page, under the team name,
|
||||
@@ -1 +0,0 @@
|
||||
If you are using a {% data variables.product.prodname_actions %} workflow, you can use a `GITHUB_TOKEN` to publish and consume packages in {% data variables.product.prodname_registry %} without needing to store and manage a {% data variables.product.pat_generic %}. For more information, see "[AUTOTITLE](/actions/security-guides/automatic-token-authentication)."
|
||||
@@ -1,5 +0,0 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** The {% data variables.product.prodname_unfurls %} API is currently in public beta and only available for use with GitHub Apps. Features and requirements may change at any time during this period.
|
||||
|
||||
{% endnote %}
|
||||
@@ -1,9 +0,0 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** To access the {% data variables.product.prodname_unfurls %} API during the preview period, you must provide a custom [media type](/rest/overview/media-types) in the `Accept` header:
|
||||
|
||||
```
|
||||
application/vnd.github.corsair-preview+json
|
||||
```
|
||||
|
||||
{% endnote %}
|
||||
@@ -1,5 +0,0 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** Insights for projects (beta) is currently in private preview and is not yet available to all organizations.
|
||||
|
||||
{% endnote %}
|
||||
@@ -1,10 +0,0 @@
|
||||
- To filter for any match of multiple values (an OR query), separate the values with a comma. For example `label:"good first issue",bug` will list all issues labelled `good first issue` or `bug`.
|
||||
- To filter for the absence of a specific value, place `-` before your filter. For example, `-label:"bug"` will only show items that do not have the label `bug`.
|
||||
- To filter for the absence of all values, enter `no:` followed by the field name. For example, `no:assignee` will only show items that do not have an assignee.
|
||||
- To filter by state, enter `is:`. For example, `is: issue` or `is:open`.
|
||||
- Separate multiple filters with a space. For example, `status:"In progress" -label:"bug" no:assignee` will show only items that have a status of `In progress`, do not have the label `bug`, and do not have an assignee.
|
||||
- To filter for the previous, current, or next iteration of an iteration field, use `@previous`, `@current`, or `@next`. For example, `iteration:@current`.
|
||||
- To filter for items assigned to the viewer, use `@me`. For example, `assignee:@me`. Anyone using this view will see items assigned to themselves.
|
||||
- To filter by when an item was last updated, use `last-updated:` followed by the number of days. This filter only supports `{number}days` (or `1day` for a single day) as a unit. For example, `last-updated:7days` will only show items that were last updated 7 or more days ago.
|
||||
- To filter date and number fields, use `>`, `>=`, `<`, `<=`, and `..` range queries. For example: `target:2022-03-01..2022-03-15`. For more information, see "[AUTOTITLE](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)." {% ifversion projects-v2-tasklists %}
|
||||
- To filter for issues tracked by a specified issue, use `tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>"` and replace `<OWNER>` with the repository owner, `<REPO>` with the repository name, and `<ISSUE NUMBER>` with the issue number. {% endif %}
|
||||
@@ -1 +0,0 @@
|
||||
Automatically generated release notes are currently in public beta and subject to change.
|
||||
@@ -1,3 +0,0 @@
|
||||
{% ifversion not ghae %}
|
||||
If your repository has a supported dependency manifest{% ifversion fpt or ghec %} (and if you've set up the dependency graph if it's a private repository){% endif %}, whenever {% data variables.product.product_name %} detects a vulnerable dependency in your repository, you will receive a weekly digest email. You can also configure your security alerts as web notifications, individual email notifications, daily email digests, or alerts in the {% data variables.product.product_name %} interface. For more information, see "[AUTOTITLE](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)."
|
||||
{% endif %}
|
||||
@@ -1 +0,0 @@
|
||||
If you use Okta as an IdP and participate in a private beta for enterprise accounts, you can manage membership in your enterprise account's organizations with SCIM. SCIM automatically invites people to or removes people from organizations in your enterprise account based on whether they are members of the group that corresponds to each organization in your IdP.
|
||||
@@ -1,3 +0,0 @@
|
||||
1. Click **Browse App Catalog**.
|
||||
|
||||
|
||||
@@ -1 +0,0 @@
|
||||
SAML SSO requires {% data variables.product.prodname_ghe_cloud %}.
|
||||
@@ -1,6 +0,0 @@
|
||||
The following IdPs can provision or deprovision user accounts on {% data variables.location.product_location %} using SCIM.
|
||||
|
||||
{% ifversion ghae %}
|
||||
- Azure AD
|
||||
- Okta (currently in beta)
|
||||
{% endif %}
|
||||
@@ -1,5 +0,0 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** You can enable or disable security features that have a one-click setup directly from the "Security coverage" view. For more information, see "[AUTOTITLE](/code-security/security-overview/assessing-adoption-code-security)."
|
||||
|
||||
{% endnote %}
|
||||
@@ -1,7 +0,0 @@
|
||||
We’ve created a phased approach to {% data variables.product.prodname_GH_advanced_security %} (GHAS) rollouts developed from industry and GitHub best practices. You can utilize this approach for your rollout, either in partnership with {% data variables.product.prodname_professional_services %} or independently.
|
||||
|
||||
While the phased approach is recommended, adjustments can be made based on the needs of your organization. We also suggest creating and adhering to a timeline for your rollout and implementation. As you begin your planning, we can work together to identify the ideal approach and timeline that works best for your organization.
|
||||
|
||||
Based on our experience helping customers with a successful deployment of GHAS, we expect most customers will want to follow their rollout in our suggested phases.
|
||||
|
||||
Depending on the needs of your organization, you may need to modify this approach and alter or remove some phases or steps.
|
||||
@@ -1 +0,0 @@
|
||||
You can authenticate as a {% data variables.product.prodname_github_app %} or as an installation.
|
||||
@@ -1 +0,0 @@
|
||||
After registering a GitHub App, you can modify your app's permissions.
|
||||
@@ -1 +0,0 @@
|
||||
This is a timestamp in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format: `YYYY-MM-DDTHH:MM:SSZ`.
|
||||
@@ -1 +0,0 @@
|
||||
1. Under "{% data variables.product.prodname_sponsors %}", next to the sponsored account, click your current tier amount, then click **Change tier**.
|
||||
@@ -1 +0,0 @@
|
||||
If you have lost access to your two-factor authentication credentials, there are a few different ways to recover your account. For more information, see "[AUTOTITLE](/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials)."
|
||||
@@ -1 +0,0 @@
|
||||
1. Type your username and password to prompt authentication.
|
||||
@@ -1 +0,0 @@
|
||||
1. Under "Automatic watching,"
|
||||
@@ -1 +0,0 @@
|
||||
Anyone can revoke their authorization of a GitHub App from their [GitHub account settings page](https://github.com/settings/apps/authorizations). Revoking the authorization of a GitHub App does not uninstall the GitHub App. You should program your GitHub App so that when it receives this webhook, it stops calling the API on behalf of the person who revoked the token. If your GitHub App continues to use a revoked access token, it will receive the `401 Bad Credentials` error.
|
||||
@@ -1 +0,0 @@
|
||||
Check run activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[AUTOTITLE](/rest/checks#runs)" REST API.
|
||||
@@ -1 +0,0 @@
|
||||
Check suite activity has occurred. {% data reusables.webhooks.action_type_desc %} For more information, see the "[AUTOTITLE](/rest/checks#suites)" REST API.
|
||||
@@ -1 +0,0 @@
|
||||
A deployment is created. {% data reusables.webhooks.action_type_desc %} For more information, see the "[AUTOTITLE](/rest/deployments/deployments#list-deployments)" REST API.
|
||||
@@ -1 +0,0 @@
|
||||
A deployment is created. {% data reusables.webhooks.action_type_desc %} For more information, see the "[AUTOTITLE](/rest/deployments/deployments)" REST API.
|
||||
@@ -1 +0,0 @@
|
||||
Activity related to a label. {% data reusables.webhooks.action_type_desc %} For more information, see the "[AUTOTITLE](/rest/issues#labels)" REST API.
|
||||
@@ -1 +0,0 @@
|
||||
Activity related to team membership. {% data reusables.webhooks.action_type_desc %} For more information, see the "[AUTOTITLE](/rest/teams#members)" REST API.
|
||||
@@ -1 +0,0 @@
|
||||
Activity related to milestones. {% data reusables.webhooks.action_type_desc %} For more information, see the "[AUTOTITLE](/rest/issues#milestones)" REST API.
|
||||
@@ -1 +0,0 @@
|
||||
Activity related to people being blocked in an organization. {% data reusables.webhooks.action_type_desc %} For more information, see the "[AUTOTITLE](/rest/orgs#blocking)" REST API.
|
||||
@@ -1 +0,0 @@
|
||||
Activity related to an organization and its members. {% data reusables.webhooks.action_type_desc %} For more information, see the "[AUTOTITLE](/rest/orgs)" REST API.
|
||||
@@ -1 +0,0 @@
|
||||
Represents an attempted build of a {% data variables.product.prodname_pages %} site, whether successful or not. A push to a {% data variables.product.prodname_pages %} enabled branch (`gh-pages` for project pages, the default branch for user and organization pages) triggers this event.
|
||||
@@ -1 +0,0 @@
|
||||
Activity related to cards in a {% data variables.projects.projects_v1_board %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[AUTOTITLE](/rest/projects#cards)" REST API.
|
||||
@@ -1 +0,0 @@
|
||||
Activity related to columns in a {% data variables.projects.projects_v1_board %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[AUTOTITLE](/rest/projects#columns)" REST API.
|
||||
@@ -1 +0,0 @@
|
||||
Activity related to {% data variables.projects.projects_v1_boards %}. {% data reusables.webhooks.action_type_desc %} For more information, see the "[AUTOTITLE](/rest/projects)" REST API.
|
||||
@@ -1 +0,0 @@
|
||||
Activity related to a repository. {% data reusables.webhooks.action_type_desc %} For more information, see the "[AUTOTITLE](/rest/repos)" REST API.
|
||||
@@ -1 +0,0 @@
|
||||
When the status of a Git commit changes. For more information, see the "[AUTOTITLE](/rest/commits/statuses)" REST API.
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user