Merge branch 'main' into add-jr-to-address
This commit is contained in:
Lee Dohm
@@ -31,6 +31,16 @@ With issue and pull request search terms, you can:
|
||||
- Filter issues and pull requests by label: `state:open type:issue label:"bug"`
|
||||
- Filter out search terms by using `-` before the term: `state:open type:issue -author:octocat`
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-next %}
|
||||
{% tip %}
|
||||
|
||||
**Tip:** You can filter issues and pull requests by label using logical OR or using logical AND.
|
||||
- To filter issues using logical OR, use the comma syntax: `label:"bug","wip"`.
|
||||
- To filter issues using logical AND, use separate label filters: `label:"bug" label:"wip"`.
|
||||
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae %}
|
||||
For issues, you can also use search to:
|
||||
|
||||
@@ -50,7 +60,7 @@ For pull requests, you can also use search to:
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Searching issues](/articles/searching-issues)"
|
||||
- "[Searching issues and pull requests](/articles/searching-issues)"
|
||||
- "[Filtering issues and pull requests](/articles/filtering-issues-and-pull-requests)"
|
||||
- "[Sorting issues and pull requests](/articles/sorting-issues-and-pull-requests)"
|
||||
- "[Sharing filters](/articles/sharing-filters)"
|
||||
|
||||
@@ -48,7 +48,7 @@ agent_start () {
|
||||
|
||||
agent_load_env
|
||||
|
||||
# agent_run_state: 0=agent running w/ key; 1=agent w/o key; 2= agent not running
|
||||
# agent_run_state: 0=agent running w/ key; 1=agent w/o key; 2=agent not running
|
||||
agent_run_state=$(ssh-add -l >| /dev/null 2>&1; echo $?)
|
||||
|
||||
if [ ! "$SSH_AUTH_SOCK" ] || [ $agent_run_state = 2 ]; then
|
||||
|
||||
@@ -16,7 +16,7 @@ topics:
|
||||
- Access management
|
||||
shortTitle: Create a PAT
|
||||
---
|
||||
Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line).
|
||||
Personal access tokens (PATs) are an alternative to using passwords for authentication to {% data variables.product.product_name %} when using the [GitHub API](/rest/overview/other-authentication-methods#via-oauth-and-personal-access-tokens) or the [command line](#using-a-token-on-the-command-line).
|
||||
|
||||
{% ifversion fpt %}If you want to use a PAT to access resources owned by an organization that uses SAML SSO, you must authorize the PAT. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing a personal access token for use with SAML single sign-on](/github/authenticating-to-github/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)."{% endif %}
|
||||
|
||||
@@ -31,16 +31,17 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti
|
||||
4. Click **Generate new token**.
|
||||
|
||||
5. Give your token a descriptive name.
|
||||
|
||||
6. Select the scopes, or permissions, you'd like to grant this token. To use your token to access repositories from the command line, select **repo**.
|
||||
{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 %}
|
||||
6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker.
|
||||
{% endif %}
|
||||
7. Select the scopes, or permissions, you'd like to grant this token. To use your token to access repositories from the command line, select **repo**.
|
||||
{% ifversion fpt or ghes %}
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
{% endif %}
|
||||
7. Click **Generate token**.
|
||||
8. Click **Generate token**.
|
||||
|
||||
8. Click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the token to your clipboard. For security reasons, after you navigate off the page, you will not be able to see the token again.
|
||||
{% ifversion fpt %}
|
||||
|
||||
{% elsif ghes > 3.1 or ghae-next %}
|
||||
@@ -50,7 +51,7 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti
|
||||
{% endif %}
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Treat your tokens like passwords and keep them secret. When working with the API, use tokens as environment variables instead of hardcoding them into your programs.
|
||||
**Warning:** Treat your tokens like passwords and keep them secret. When working with the API, use tokens as environment variables instead of hardcoding them into your programs.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@ intro: 'You can add a CITATION file to your repository to help users correctly c
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>=3.3'
|
||||
ghae: '>=M3'
|
||||
ghae: 'issue-4651'
|
||||
topics:
|
||||
- Repositories
|
||||
---
|
||||
|
||||
@@ -15,7 +15,7 @@ topics:
|
||||
---
|
||||
## About READMEs
|
||||
|
||||
You can add a README file to a repository to communicate important information about your project. A README, along with a repository license{% ifversion fpt or ghes > 3.1 or ghae-issue-4651 %}, citation file{% endif %}{% ifversion fpt %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions.
|
||||
You can add a README file to a repository to communicate important information about your project. A README, along with a repository license{% ifversion fpt or ghes > 3.2 or ghae-issue-4651 %}, citation file{% endif %}{% ifversion fpt %}, contribution guidelines, and a code of conduct{% elsif ghes %} and contribution guidelines{% endif %}, communicates expectations for your project and helps you manage contributions.
|
||||
|
||||
For more information about providing guidelines for your project, see {% ifversion fpt %}"[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and {% endif %}"[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
|
||||
|
||||
|
||||
@@ -31,10 +31,7 @@ If an automatic build of code for a compiled language within your project fails,
|
||||
|
||||
```yaml
|
||||
jobs:
|
||||
analyze:{% ifversion fpt or ghes > 3.1 or ghae-next %}
|
||||
permissions:
|
||||
security-events: write
|
||||
actions: read{% endif %}
|
||||
analyze:
|
||||
...
|
||||
strategy:
|
||||
fail-fast: false
|
||||
|
||||
@@ -148,7 +148,8 @@ You can narrow your results by labels, using the `label` qualifier. Since issues
|
||||
| ------------- | -------------
|
||||
| <code>label:<em>LABEL</em></code> | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories.
|
||||
| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority."
|
||||
| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."
|
||||
| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae-next %}
|
||||
| | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %}
|
||||
|
||||
## Search by milestone
|
||||
|
||||
|
||||
@@ -28,7 +28,10 @@ shortTitle: Enforce SSO for organizations
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Enabling authentication with SAML single sign-on for your enterprise account will override any existing organization-level SAML configurations.
|
||||
**Notes:**
|
||||
|
||||
- When you enable SAML SSO for your enterprise, the enterprise configuration will override any existing organization-level SAML configurations.
|
||||
- When you enforce SAML SSO for an organization, {% data variables.product.company_short %} removes any members of the organization that have not authenticated successfully with your SAML IdP. When you require SAML SSO for your enterprise, {% data variables.product.company_short %} does not remove members of the enterprise that have not authenticated successfully with your SAML IdP. The next time a member accesses the enterprise's resources, the member must authenticate with your SAML IdP.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
|
||||
@@ -1,7 +1,8 @@
|
||||
---
|
||||
title: Inviting people to manage your enterprise
|
||||
intro: You can invite people to become enterprise owners or billing managers in your enterprise account. You can also remove enterprise owners or billing managers who no longer need access to the enterprise account.
|
||||
intro: You can {% ifversion fpt %}invite people to become enterprise owners or billing managers for{% elsif ghes %}add enterprise owners to{% endif %} your enterprise account. You can also remove enterprise owners {% ifversion fpt %}or billing managers {% endif %}who no longer need access to the enterprise account.
|
||||
product: '{% data reusables.gated-features.enterprise-accounts %}'
|
||||
permissions: 'Enterprise owners can {% ifversion fpt %}invite other people to become{% elsif ghes %}add{% endif %} additional enterprise administrators.'
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise-account/inviting-people-to-manage-your-enterprise-account
|
||||
- /articles/inviting-people-to-collaborate-in-your-business-account/
|
||||
@@ -11,12 +12,21 @@ versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
topics:
|
||||
- Administrator
|
||||
- Enterprise
|
||||
- User account
|
||||
shortTitle: Invite people to manage
|
||||
---
|
||||
## About inviting people to manage your enterprise account
|
||||
|
||||
{% data reusables.enterprise-accounts.enterprise-administrators %} For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise).
|
||||
## About users who can manage your enterprise account
|
||||
|
||||
{% data reusables.enterprise-accounts.enterprise-administrators %} For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise)."
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
If you want to manage owners and billing managers for an enterprise account on {% data variables.product.prodname_dotcom_the_website %}, see "[Inviting people to manage your enterprise](/free-pro-team@latest/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)" in the {% data variables.product.prodname_dotcom_the_website %} documentation.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
@@ -24,24 +34,28 @@ shortTitle: Invite people to manage
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Inviting an enterprise administrator to your enterprise account
|
||||
## {% ifversion fpt %}Inviting{% elsif ghes %}Adding{% endif %} an enterprise administrator to your enterprise account
|
||||
|
||||
Only enterprise owners can invite other people to become enterprise administrators.
|
||||
|
||||
After you invite someone to join the enterprise account, they must accept the emailed invitation before they can access the enterprise account.
|
||||
{% ifversion fpt %}After you invite someone to join the enterprise account, they must accept the emailed invitation before they can access the enterprise account.{% endif %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.people-tab %}
|
||||
3. In the left sidebar, click **Administrators**.
|
||||
1. In the left sidebar, click **Administrators**.
|
||||
|
||||
4. Above the list of administrators, click **Invite admin**.
|
||||
|
||||
5. Type the username, full name, or email address of the person you want to invite to become an enterprise administrator, then select the appropriate person from the results.
|
||||
|
||||
6. Select **Owner** or **Billing Manager**.
|
||||
1. Above the list of administrators, click {% ifversion fpt %}**Invite admin**{% elsif ghes %}**Add owner**{% endif %}.
|
||||
{% ifversion fpt %}
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
{% endif %}
|
||||
1. Type the username, full name, or email address of the person you want to invite to become an enterprise administrator, then select the appropriate person from the results.
|
||||
{% ifversion fpt %}
|
||||
1. Select **Owner** or **Billing Manager**.
|
||||
|
||||
7. Click **Send Invitation**.
|
||||
|
||||
1. Click **Send Invitation**.
|
||||
{% endif %}{% ifversion ghes %}
|
||||
1. Click **Add**.
|
||||
{% endif %}
|
||||
|
||||
## Removing an enterprise administrator from your enterprise account
|
||||
|
||||
@@ -49,5 +63,10 @@ Only enterprise owners can remove other enterprise administrators from the enter
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.people-tab %}
|
||||
3. Next to the username of the person you'd like to remove, click {% octicon "gear" aria-label="The Settings gear" %}, then click **Remove owner** or **Remove billing manager**.
|
||||
1. Next to the username of the person you'd like to remove, click {% octicon "gear" aria-label="The Settings gear" %}, then click **Remove owner**{% ifversion fpt %} or **Remove billing manager**{% endif %}.
|
||||
{% ifversion fpt %}
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
{% endif %}
|
||||
1. Read the confirmation, then click **Remove owner**{% ifversion fpt %} or **Remove billing manager**{% endif %}.
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About enterprise accounts
|
||||
intro: 'With {% data variables.product.prodname_ghe_cloud %}, you can create an enterprise account to enable collaboration between your organizations, while giving administrators a single point of visibility and management.'
|
||||
intro: 'With {% data variables.product.product_name %}, you can use an enterprise account to {% ifversion fpt %}enable collaboration between your organizations, while giving{% elsif ghes or ghae %}give{% endif %} administrators a single point of visibility and management.'
|
||||
product: '{% data reusables.gated-features.enterprise-accounts %}'
|
||||
redirect_from:
|
||||
- /articles/about-github-business-accounts/
|
||||
@@ -11,37 +11,8 @@ versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Enterprise
|
||||
---
|
||||
## About enterprise accounts
|
||||
|
||||
An enterprise account allows you to manage multiple {% data variables.product.prodname_dotcom %} organizations and {% data variables.product.prodname_ghe_server %} instances. Your enterprise account must have a handle, like an organization or personal account on {% data variables.product.prodname_dotcom %}. Enterprise administrators can manage settings and preferences, like:
|
||||
|
||||
- Member access and management (organization members, outside collaborators)
|
||||
- Billing and usage ({% data variables.product.prodname_ghe_server %} instances, user licenses, {% data variables.large_files.product_name_short %} packs{% ifversion fpt or ghes > 3.0 %}, {% data variables.product.prodname_GH_advanced_security %} usage{% endif %})
|
||||
- Security (single sign-on, two factor authentication)
|
||||
- Requests and support bundle sharing with {% data variables.contact.enterprise_support %}
|
||||
|
||||
{% data reusables.enterprise-accounts.enterprise-accounts-billing %} For more information about managing your {% data variables.product.prodname_ghe_cloud %} subscription, see "[Viewing the subscription and usage for your enterprise account](/articles/viewing-the-subscription-and-usage-for-your-enterprise-account)." For more information about managing your {% data variables.product.prodname_ghe_server %} billing settings, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
|
||||
|
||||
For more information about the differences between {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %}, see "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)." To upgrade to {% data variables.product.prodname_enterprise %} or to get started with an enterprise account, contact {% data variables.contact.contact_enterprise_sales %}.
|
||||
|
||||
For more information about member access and management, see "{% ifversion fpt %}[Managing users in your enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise){% elsif ghae or ghes %}[Managing users, organizations, and repositories](/admin/user-management){% endif %}."
|
||||
|
||||
For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)."
|
||||
|
||||
{% ifversion fpt %}
|
||||
|
||||
## Managing organizations linked to your enterprise account
|
||||
|
||||
Organizations are shared accounts where groups of people can collaborate across many projects at once. Owners can manage member access to the organization's data and projects with sophisticated security and administrative features. For more information, see "[About organizations](/articles/about-organizations)."
|
||||
|
||||
Enterprise owners can create organizations and link them to the enterprise. After you add organizations to your enterprise account, you can manage and enforce the organizations' policies. Specific enforcement options vary by setting; generally, you can choose to enforce a single policy for every organization in your enterprise account or allow owners to set policy on the organization level.
|
||||
|
||||
For more information, see "[Managing organizations in your enterprise account](/articles/managing-organizations-in-your-enterprise-account)" and "[Setting policies for organizations in your enterprise account](/articles/setting-policies-for-organizations-in-your-enterprise-account)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Managing {% data variables.product.prodname_ghe_server %} licenses linked to your enterprise account
|
||||
|
||||
{% data reusables.enterprise-accounts.admin-managing-licenses %}
|
||||
{% data reusables.enterprise-accounts.about-enterprise-accounts %}
|
||||
|
||||
@@ -11,7 +11,6 @@ topics:
|
||||
children:
|
||||
- /about-enterprise-accounts
|
||||
- /verifying-or-approving-a-domain-for-your-enterprise-account
|
||||
- /viewing-the-subscription-and-usage-for-your-enterprise-account
|
||||
- /managing-licenses-for-visual-studio-subscription-with-github-enterprise
|
||||
- /connecting-an-azure-subscription-to-your-enterprise
|
||||
shortTitle: Manage your enterprise
|
||||
|
||||
@@ -44,7 +44,7 @@ For more information, see "[Inviting users to join your organization](/organizat
|
||||
|
||||
## Viewing {% data variables.product.prodname_enterprise %} licensing
|
||||
|
||||
After assigning a license for {% data variables.product.prodname_vss_ghe %} in {% data variables.product.prodname_vss_admin_portal_with_url %}, you can view the number of {% data variables.product.prodname_enterprise %} licenses available to your enterprise account. For more information, see "[Viewing the subscription and usage for your enterprise account](/github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account)."
|
||||
After assigning a license for {% data variables.product.prodname_vss_ghe %} in {% data variables.product.prodname_vss_admin_portal_with_url %}, you can view the number of {% data variables.product.prodname_enterprise %} licenses available to your enterprise account. For more information, see "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
|
||||
|
||||
You can also see pending {% data variables.product.prodname_enterprise %} invitations to subscribers in {% data variables.product.prodname_vss_admin_portal_with_url %}. The list of pending invitations includes subscribers who are not yet members of at least one organization in your enterprise account. For more information, see "[Viewing people in your enterprise](/github/setting-up-and-managing-your-enterprise/viewing-people-in-your-enterprise#viewing-members-and-outside-collaborators)."
|
||||
|
||||
|
||||
@@ -1,47 +0,0 @@
|
||||
---
|
||||
title: Viewing the subscription and usage for your enterprise account
|
||||
intro: 'You can view the current subscription, license usage, invoices, payment history, and other billing information for your enterprise account.'
|
||||
product: '{% data reusables.gated-features.enterprise-accounts %}'
|
||||
permissions: Enterprise owners and billing managers can access and manage all billing settings for enterprise accounts.
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise-account/viewing-the-subscription-and-usage-for-your-enterprise-account
|
||||
- /articles/viewing-the-subscription-and-usage-for-your-enterprise-account
|
||||
- /github/setting-up-and-managing-your-enterprise/viewing-the-subscription-and-usage-for-your-enterprise-account
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
topics:
|
||||
- Enterprise
|
||||
shortTitle: View subscription & usage
|
||||
---
|
||||
## About billing for enterprise accounts
|
||||
|
||||
Enterprise accounts are currently available to {% data variables.product.prodname_enterprise %} customers paying by invoice. Billing for all of the organizations and {% data variables.product.prodname_ghe_server %} instances connected to your enterprise account are aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom_the_website %} services (including paid licenses in organizations, {% data variables.large_files.product_name_long %} data packs,{% ifversion fpt or ghes > 3.0 %} {% data variables.product.prodname_GH_advanced_security %} usage,{% endif %} and subscriptions for {% data variables.product.prodname_marketplace %} apps).
|
||||
|
||||
{% ifversion fpt %}{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/github/setting-up-and-managing-your-enterprise/connecting-an-azure-subscription-to-your-enterprise)."{% endif %}
|
||||
|
||||
For more information about managing billing managers, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)."
|
||||
|
||||
## Viewing the subscription and usage for your enterprise account
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.license-tab %}
|
||||
1. Under "User {% ifversion fpt %}Licenses{% else %}licenses{% endif %}", view your total licenses, number of consumed licenses, and your subscription expiration date.
|
||||
{% ifversion fpt %}{% else %}
|
||||
{% endif %}
|
||||
1. Optionally, to view details for license usage or download a {% ifversion fpt %}CSV{% elsif ghes %}JSON{% endif %} file with license details{% ifversion fpt %}, to the right of "User Licenses"{% endif %}, click **View {% ifversion fpt %}details{% elsif ghes %}users{% endif %}** or {% ifversion fpt %}{% octicon "download" aria-label="The download icon" %}{% elsif ghes %}**Export license usage**{% endif %}.{% ifversion fpt %}
|
||||
{% endif %}
|
||||
{% ifversion fpt or ghes > 3.0 %}
|
||||
1. Optionally, to view usage details for other features, in the left sidebar, click **Billing**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt %}
|
||||
## Further reading
|
||||
|
||||
- "[About billing for GitHub Actions](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#about-billing-for-github-actions)"
|
||||
- "[About billing for Git Large File Storage](/billing/managing-billing-for-git-large-file-storage/about-billing-for-git-large-file-storage)"
|
||||
- "[About licensing for {% data variables.product.prodname_GH_advanced_security %}](/billing/managing-licensing-for-github-advanced-security/about-licensing-for-github-advanced-security)"
|
||||
|
||||
{% endif %}
|
||||
@@ -15,7 +15,7 @@ topics:
|
||||
|
||||
Welcome to GitHub's Guide to the Digital Millennium Copyright Act, commonly known as the "DMCA." This page is not meant as a comprehensive primer to the statute. However, if you've received a DMCA takedown notice targeting content you've posted on GitHub or if you're a rights-holder looking to issue such a notice, this page will hopefully help to demystify the law a bit as well as our policies for complying with it.
|
||||
|
||||
(If you just want to submit a notice, you can [skip to the end](#f-submitting-notices).)
|
||||
(If you just want to submit a notice, you can skip to "[G. Submitting Notices](#g-submitting-notices).")
|
||||
|
||||
As with all legal matters, it is always best to consult with a professional about your specific questions or situation. We strongly encourage you to do so before taking any action that might impact your rights. This guide isn't legal advice and shouldn't be taken as such.
|
||||
|
||||
@@ -85,7 +85,7 @@ Where our experts determine that a claim is complete, legal, and technically leg
|
||||
|
||||
Please note, our review process for circumvention technology does not apply to content that would otherwise violate our Acceptable Use Policy restrictions against sharing unauthorized product licensing keys, software for generating unauthorized product licensing keys, or software for bypassing checks for product licensing keys. Although these types of claims may also violate the DMCA provisions on circumvention technology, these are typically straightforward and do not warrant additional technical and legal review. Nonetheless, where a claim is not straightforward, for example in the case of jailbreaks, the circumvention technology claim review process would apply.
|
||||
|
||||
When GitHub processes a DMCA takedown under our circumvention technology claim review process, we will offer to connect the repository owner with legal resources, in case the repository owner wishes to obtain third party legal advice.
|
||||
When GitHub processes a DMCA takedown under our circumvention technology claim review process, we will offer the repository owner a referral to receive independent legal consultation through [GitHub’s Developer Defense Fund](https://github.blog/2021-07-27-github-developer-rights-fellowship-stanford-law-school/) at no cost to them.
|
||||
|
||||
## D. What If I Inadvertently Missed the Window to Make Changes?
|
||||
|
||||
|
||||
Reference in New Issue
Block a user