Merge branch 'main' into backtick
This commit is contained in:
Janice
@@ -12,7 +12,13 @@ versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '>=3.0'
|
||||
github-ae: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Dependabot
|
||||
- Alerts
|
||||
- Advanced Security
|
||||
- Dependency graph
|
||||
- Secret scanning
|
||||
- Repositories
|
||||
---
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
@@ -3,8 +3,13 @@ title: Reviewing dependency changes in a pull request
|
||||
intro: 'If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Pull requests
|
||||
- Dependency review
|
||||
- Advanced Security
|
||||
- Vulnerabilities
|
||||
- Dependencies
|
||||
redirect_from:
|
||||
- /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request
|
||||
- /github/collaborating-with-issues-and-pull-requests/reviewing-dependency-changes-in-a-pull-request
|
||||
|
||||
@@ -13,27 +13,27 @@ versions:
|
||||
topics:
|
||||
- Pull requests
|
||||
---
|
||||
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
|
||||
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
|
||||
|
||||
#### Deleting a private repository
|
||||
### Deleting a private repository
|
||||
|
||||
When you delete a private repository, all of its private forks are also deleted.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
|
||||
|
||||
#### Deleting a public repository
|
||||
### Deleting a public repository
|
||||
|
||||
When you delete a public repository, one of the existing public forks is chosen to be the new parent repository. All other repositories are forked off of this new parent and subsequent pull requests go to this new parent.
|
||||
|
||||
{% endif %}
|
||||
|
||||
#### Private forks and permissions
|
||||
### Private forks and permissions
|
||||
|
||||
{% data reusables.repositories.private_forks_inherit_permissions %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
|
||||
|
||||
#### Changing a public repository to a private repository
|
||||
### Changing a public repository to a private repository
|
||||
|
||||
If a public repository is made private, its public forks are split off into a new network. As with deleting a public repository, one of the existing public forks is chosen to be the new parent repository and all other repositories are forked off of this new parent. Subsequent pull requests go to this new parent.
|
||||
|
||||
@@ -43,15 +43,15 @@ In other words, a public repository's forks will remain public in their own sepa
|
||||
If a public repository has anonymous Git read access enabled and the repository is made private, all of the repository's forks will lose anonymous Git read access and return to the default disabled setting. If a forked repository is made public, repository administrators can re-enable anonymous Git read access. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
|
||||
{% endif %}
|
||||
|
||||
##### Deleting the private repository
|
||||
#### Deleting the private repository
|
||||
|
||||
If a public repository is made private and then deleted, its public forks will continue to exist in a separate network.
|
||||
|
||||
#### Changing a private repository to a public repository
|
||||
### Changing a private repository to a public repository
|
||||
|
||||
If a private repository is made public, each of its private forks is turned into a standalone private repository and becomes the parent of its own new repository network. Private forks are never automatically made public because they could contain sensitive commits that shouldn't be exposed publicly.
|
||||
|
||||
##### Deleting the public repository
|
||||
#### Deleting the public repository
|
||||
|
||||
If a private repository is made public and then deleted, its private forks will continue to exist as standalone private repositories in separate networks.
|
||||
|
||||
@@ -59,7 +59,7 @@ If a private repository is made public and then deleted, its private forks will
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
|
||||
|
||||
#### Changing the visibility of an internal repository
|
||||
### Changing the visibility of an internal repository
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -69,7 +69,7 @@ If a private repository is made public and then deleted, its private forks will
|
||||
|
||||
If the policy for your enterprise permits forking, any fork of an internal repository will be private. If you change the visibility of an internal repository, any fork owned by an organization or user account will remain private.
|
||||
|
||||
##### Deleting the internal repository
|
||||
#### Deleting the internal repository
|
||||
|
||||
If you change the visibility of an internal repository and then delete the repository, the forks will continue to exist in a separate network.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Exploring projects on GitHub
|
||||
intro: ''
|
||||
intro: 'Discover interesting projects on {% data variables.product.product_name %} and contribute to open source by collaborating with other people.'
|
||||
redirect_from:
|
||||
- /categories/stars/
|
||||
- /categories/87/articles/
|
||||
@@ -17,4 +17,3 @@ children:
|
||||
- /saving-repositories-with-stars
|
||||
- /following-people
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Getting started with Git
|
||||
intro: ''
|
||||
intro: 'Set up Git, a distributed version control system, to manage your {% data variables.product.product_name %} repositories from your computer.'
|
||||
redirect_from:
|
||||
- /articles/getting-started-with-git-and-github
|
||||
- /github/using-git/getting-started-with-git-and-github
|
||||
@@ -22,4 +22,3 @@ children:
|
||||
- /configuring-git-to-handle-line-endings
|
||||
- /ignoring-files
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Learning about GitHub
|
||||
intro: '{% data variables.product.prodname_dotcom %} has a variety of products and account types to help you build software and collaborate with other people.'
|
||||
intro: 'Learn how you can use {% data variables.product.company_short %} products to improve your software management process and collaborate with other people.'
|
||||
redirect_from:
|
||||
- /articles/learning-about-github
|
||||
versions:
|
||||
@@ -21,4 +21,3 @@ children:
|
||||
- /access-permissions-on-github
|
||||
- /faq-about-changes-to-githubs-plans
|
||||
---
|
||||
|
||||
|
||||
@@ -19,7 +19,7 @@ topics:
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" %}
|
||||
|
||||
You can store a variety of projects in {% data variables.product.product_name %} repositories, including open source projects. With [open source projects](http://opensource.org/about), you can share code to make better, more reliable software.
|
||||
You can store a variety of projects in {% data variables.product.product_name %} repositories, including open source projects. With [open source projects](http://opensource.org/about), you can share code to make better, more reliable software. You can use repositories to collaborate with others and track your work. For more information, see "[About repositories](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)."
|
||||
|
||||
{% elsif enterpriseServerVersions contains currentVersion or currentVersion == "github-ae@latest" %}
|
||||
|
||||
@@ -82,6 +82,7 @@ Congratulations! You have now created a repository, including a *README* file, a
|
||||
|
||||
- "[Set up Git](/articles/set-up-git)"
|
||||
- **Create a repository**
|
||||
- "[Clone a repository](/github/creating-cloning-and-archiving-repositories/cloning-a-repository)"
|
||||
- "[Fork a repository](/articles/fork-a-repo)"
|
||||
- "[Be social](/articles/be-social)"
|
||||
- {% data reusables.support.connect-in-the-forum-bootcamp %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Quickstart
|
||||
intro: 'Quickly get started with common tasks on {% data variables.product.prodname_dotcom %}.'
|
||||
intro: 'Get started using {% data variables.product.product_name %} to manage Git repositories and collaborate with others.'
|
||||
versions:
|
||||
free-pro-team: '*'
|
||||
enterprise-server: '*'
|
||||
@@ -21,4 +21,3 @@ children:
|
||||
- /git-cheatsheet
|
||||
- /git-and-github-learning-resources
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Signing up for GitHub
|
||||
intro: ''
|
||||
intro: 'Start using {% data variables.product.prodname_dotcom %} for yourself or your team.'
|
||||
redirect_from:
|
||||
- /articles/signing-up-for-github
|
||||
versions:
|
||||
@@ -15,4 +15,3 @@ children:
|
||||
- /setting-up-a-trial-of-github-enterprise-cloud
|
||||
- /setting-up-a-trial-of-github-enterprise-server
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using Git
|
||||
intro: ''
|
||||
intro: 'Use Git to manage your {% data variables.product.product_name %} repositories from your computer.'
|
||||
redirect_from:
|
||||
- /articles/using-common-git-commands
|
||||
- /github/using-git/using-common-git-commands
|
||||
@@ -23,4 +23,3 @@ children:
|
||||
- /using-git-rebase-on-the-command-line
|
||||
- /resolving-merge-conflicts-after-a-git-rebase
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Using GitHub
|
||||
intro: ''
|
||||
intro: "Explore {% data variables.product.company_short %}'s products from different platforms and devices."
|
||||
redirect_from:
|
||||
- /articles/using-github
|
||||
versions:
|
||||
@@ -16,4 +16,3 @@ children:
|
||||
- /keyboard-shortcuts
|
||||
- /troubleshooting-connectivity-problems
|
||||
---
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ You can also use {% data variables.large_files.product_name_short %} with {% dat
|
||||
|
||||
{% data reusables.large_files.can-include-lfs-objects-archives %}
|
||||
|
||||
#### Pointer file format
|
||||
### Pointer file format
|
||||
|
||||
{% data variables.large_files.product_name_short %}'s pointer file looks like this:
|
||||
|
||||
|
||||
@@ -1,5 +1,6 @@
|
||||
---
|
||||
title: Searching for information on GitHub
|
||||
intro: Use different types of searches to find the information you want.
|
||||
redirect_from:
|
||||
- /categories/78/articles/
|
||||
- /categories/search/
|
||||
@@ -14,4 +15,3 @@ children:
|
||||
- /getting-started-with-searching-on-github
|
||||
- /searching-on-github
|
||||
---
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ For more information about adding people to your enterprise, see "{% if currentV
|
||||
|
||||
Enterprise owners have complete control over the enterprise and can take every action, including:
|
||||
- Managing administrators
|
||||
- {% if currentVersion == "free-pro-team@latest" %}Adding and removing {% elsif currentVersion == "github-ae@latest" %}Managing{% endif %} organizations {% if currentVersion == "free-pro-team@latest" %}to and from {% elsif currentVersion == "github-ae@latest" %} in{% endif %} the enterprise
|
||||
- {% if currentVersion == "free-pro-team@latest" %}Adding and removing {% elsif currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %}Managing{% endif %} organizations {% if currentVersion == "free-pro-team@latest" %}to and from {% elsif currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.20" %} in{% endif %} the enterprise
|
||||
- Managing enterprise settings
|
||||
- Enforcing policy across organizations
|
||||
{% if currentVersion == "free-pro-team@latest" %}- Managing billing settings{% endif %}
|
||||
|
||||
@@ -127,6 +127,8 @@ When you participate in certain programs, {% data variables.product.prodname_dot
|
||||
|  | **{% data variables.product.prodname_dotcom %} Sponsor** | If you sponsored an open source contributor through {% data variables.product.prodname_sponsors %} you'll get a {% data variables.product.prodname_dotcom %} Sponsor badge on your profile. Clicking the badge takes you to the **Sponsoring** tab of your profile. For more information, see "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)." |
|
||||
| {% octicon "cpu" aria-label="The Developer Program icon" %} | **Developer Program Member** | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% data variables.product.prodname_dotcom %} API, you'll get a Developer Program Member badge on your profile. For more information on the {% data variables.product.prodname_dotcom %} Developer Program, see [GitHub Developer](/program/). |
|
||||
| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. For more information about {% data variables.product.prodname_pro %}, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products#github-pro)." |
|
||||
| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | If you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the {% data variables.product.prodname_dotcom %} Security program, see [{% data variables.product.prodname_dotcom %} Security](https://bounty.github.com/). |
|
||||
| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **Github Campus Expert** | If you participate in the {% data variables.product.prodname_dotcom %} Campus Program you'll get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. For more information about the Campus Experts program, see [Campus Experts](https://education.github.com/experts). |
|
||||
|
||||
### Disabling badges on your profile
|
||||
|
||||
@@ -141,7 +143,7 @@ You can disable some of the badges for {% data variables.product.prodname_dotcom
|
||||
|
||||
### List of qualifying repositories for Mars 2020 Helicopter Contributor badge
|
||||
|
||||
If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor badge on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
|
||||
If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor badge on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. You can be the original author or [one of the co-authors](/github/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) of the commit. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
|
||||
|
||||
| {% data variables.product.prodname_dotcom %} Repository | Version | Tag |
|
||||
|---|---|---|
|
||||
|
||||
@@ -15,7 +15,7 @@ PLEASE READ THIS ADDENDUM CAREFULLY AS IT AMENDS THE TERMS OF YOUR ENTERPRISE LI
|
||||
|
||||
BY ACCESSING GITHUB CONNECT, YOU ACCEPT ALL THE TERMS AND CONDITIONS OF THIS ADDENDUM. IF YOU ARE ENTERING INTO THIS ADDENDUM ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY (“CUSTOMER”), YOU REPRESENT THAT YOU HAVE THE LEGAL AUTHORITY TO BIND CUSTOMER TO THIS AGREEMENT.
|
||||
|
||||
#### 1. GitHub.com’s Terms of Service and the GitHub Enterprise Software License Agreement Will Apply; Pricing
|
||||
### 1. GitHub.com’s Terms of Service and the GitHub Enterprise Software License Agreement Will Apply; Pricing
|
||||
|
||||
Customer can enable unified integrations, which allow Customer’s Enterprise users to connect with GitHub.com (“GitHub Connect”). In order to access GitHub Connect, Customer must have at least one (1) account on GitHub.com and one (1) licensed instance of GitHub Enterprise. Customer’s access to GitHub Connect will also be governed by its applicable GitHub.com Terms of Service and the Agreement which are hereby incorporated by reference, (the "Generally Applicable Terms"), such that the Generally Applicable Terms will apply concurrently. In the event of a direct conflict between this Addendum and the Generally Applicable Terms, the Generally Applicable Terms will control, except with respect to any use of GitHub Connect, in which case this Addendum will control.
|
||||
|
||||
@@ -23,41 +23,41 @@ Customer may not use GitHub Connect to violate its Generally Applicable Terms. A
|
||||
|
||||
Participation in GitHub Connect is provided at no additional charge through the Addendum Term (as defined below).
|
||||
|
||||
#### 2. Confidentiality
|
||||
### 2. Confidentiality
|
||||
|
||||
To the extent they do not conflict with the confidentiality obligations provided in the GitHub Enterprise Software License Agreement, GitHub Connect including any Confidential Information will be governed by the confidentiality obligations stated herein.
|
||||
|
||||
For the purposes of this Addendum, "Confidential Information" means any business or technical information shared with the other party (specifically excluding any Content or information created or shared on the Service or Website, which Content or information is governed by other provisions in this Addendum and the Generally Applicable Terms) that either one of us discloses to the other, in writing, orally, or by any other means, and including things like computer programs, code, algorithms, data, know-how, formulas, processes, ideas, inventions (whether patentable or not), schematics and other technical, business, financial, and product development plans, names and expertise of employees and consultants, and customer lists. Each party agrees to maintain the other party's Confidential Information in confidence using at least the same degree of care as it uses in safeguarding its own Confidential Information, subject to a minimum standard of reasonable diligence and protection.
|
||||
|
||||
#### 3. Term and Termination
|
||||
### 3. Term and Termination
|
||||
|
||||
This Addendum begins on the Addendum Effective Date and continues for the duration of the License Term as defined in the Generally Applicable Terms (“Addendum Term”). This Addendum may be terminated in accordance with the Generally Applicable Terms. This Addendum will terminate immediately, without the requirement of notice, if Customer breaches any term of this Addendum or the Generally Applicable Terms.
|
||||
|
||||
The rights and obligations in Sections 1, 2, 4 through 12, or which should naturally survive the termination or expiration of an agreement will survive the termination or expiration of this Addendum or the Generally Applicable Terms. Upon termination or expiration of this Addendum all of the rights and licenses granted to Customer in this Addendum will immediately cease to exist, Customer must destroy (or, at GitHub’s request, return) all of GitHub’s Confidential Information and any copies (including electronic copies) which are in Customer’s possession or control, and certify in writing compliance with these requirements.
|
||||
|
||||
#### 4. Warranties and Disclaimers
|
||||
### 4. Warranties and Disclaimers
|
||||
|
||||
Customer warrants that it: (i) has the authority to execute this Addendum and to perform its obligations; (ii) will make no false or misleading statements or representations regarding GitHub or GitHub’s products and services; and (iii) will not take on any obligation or responsibility, or make any representation, warranty, guarantee or endorsement to anyone on GitHub’s behalf (including, without limitation, any of our products or services).
|
||||
|
||||
CUSTOMER UNDERSTANDS AND AGREES THAT ANY MATERIALS OR INFORMATION IT IS PROVIDED OR THAT IT HAS ACCESS TO UNDER THIS ADDENDUM (INCLUDING, WITHOUT LIMITATION, ANY CONFIDENTIAL INFORMATION OR PRE-RELEASE MATERIALS) ARE PROVIDED “AS IS”, AND WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. GITHUB SPECIFICALLY DISCLAIMS ANY AND ALL IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.
|
||||
|
||||
#### 5. Indemnity
|
||||
### 5. Indemnity
|
||||
|
||||
Customer agrees to indemnify, defend and hold GitHub harmless from and against any and all claims which may arise under or out of Customer’s participation in GitHub Connect; Customer’s negligence or intentional misconduct; any misrepresentations Customer makes with respect to GitHub or GitHub’s products or services; or Customer’s violation of any part of this Addendum.
|
||||
|
||||
#### 6. Limitation of Liability
|
||||
### 6. Limitation of Liability
|
||||
|
||||
IN NO EVENT WILL EITHER PARTY BE LIABLE TO THE OTHER OR TO ANY THIRD PARTY FOR ANY INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO DAMAGES FOR LOST DATA, LOST PROFITS OR COSTS OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, TORT (INCLUDING WITHOUT LIMITATION PRODUCTS LIABILITY, STRICT LIABILITY AND NEGLIGENCE), OR ANY OTHER THEORY, AND WHETHER OR NOT THE PARTY KNEW OR SHOULD HAVE KNOWN ABOUT THE POSSIBILITY OF SUCH DAMAGE. IN NO EVENT WILL GITHUB’S AGGREGATE LIABILITY TO CUSTOMER ARISING OUT OF OR RELATED TO THIS ADDENDUM FOR ANY CAUSE WHATSOEVER, AND REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT OR IN TORT, EXCEED THE GREATER OF (I) AMOUNTS ACTUALLY PAID UNDER THIS ADDENDUM; OR (II) FIVE HUNDRED DOLLARS ($500). THE FOREGOING LIMITATIONS WILL APPLY NOTWITHSTANDING THE FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY STATED IN THIS ADDENDUM.
|
||||
|
||||
#### 7. Proprietary Rights
|
||||
### 7. Proprietary Rights
|
||||
|
||||
Customer agrees that GitHub and its licensors own all right, title and interest in and to all GitHub products and services; all information and data relating to their configurations and combinations; and all modifications to and derivative works of any of the foregoing. Customer must not remove, alter, cover or obfuscate any copyright or other proprietary rights notices that GitHub places on or embeds in GitHub Connect, or any other GitHub products and services.
|
||||
|
||||
#### 8. Independent Development
|
||||
### 8. Independent Development
|
||||
|
||||
Nothing in this Addendum will impair GitHub’s right to develop, acquire, license, market, promote or distribute products, software or technologies that might compete with Customer’s.
|
||||
|
||||
#### 9. Privacy
|
||||
### 9. Privacy
|
||||
|
||||
GitHub may collect information about how Customer uses GitHub Connect and how GitHub can improve it. Customer may enable GitHub Connect to authorize GitHub to collect protected data, which includes private repository data and Customer Personal Information (as defined in the GitHub Privacy Statement), from Customer's Enterprise account. If Customer connects its Enterprise instance with its GitHub.com account, Customer sends identifying instance information to GitHub.com, which information is governed by [GitHub’s Privacy Statement](/articles/github-privacy-statement/). By enabling this configuration, Customer agrees that it is responsible for the actions that are performed on or through its account, subject to the terms of its Generally Applicable Terms.
|
||||
|
||||
@@ -65,14 +65,14 @@ GitHub may collect certain additional personal information from Customer in GitH
|
||||
|
||||
GitHub's servers are located in the United States. GitHub processes and controls Customer’s data in the United States. However, Customer is solely responsible for determining what personal data it submits to GitHub. Please refer to our [Privacy Statement](/articles/github-privacy-statement/) for more information.
|
||||
|
||||
#### 10. Feedback
|
||||
### 10. Feedback
|
||||
|
||||
Customer may, at its option, provide ideas, know-how, algorithms, code contributions, suggestions, enhancement requests, recommendations or any other feedback for GitHub Connect or GitHub’s other products or services (collectively, “Feedback”). If Customer provides Feedback, it acknowledges and agrees that GitHub will have a royalty-free, fully paid-up, worldwide, transferable, sub-licensable, irrevocable and perpetual license to implement, use, modify, commercially exploit or incorporate the Feedback into its products, services, and documentation.
|
||||
|
||||
#### 11. Entire Agreement
|
||||
### 11. Entire Agreement
|
||||
|
||||
This Addendum and the Generally Applicable Terms contain the entire agreement of the parties with respect to its subject matter and supersede all prior communications, representations, understandings and agreements, whether written or oral. The terms or conditions of any of Customer’s purchase orders, acknowledgements, or other documents sent in connection with this Addendum will be null and void, and of no effect.
|
||||
|
||||
#### 12. No Other Modifications; Order of Precedence
|
||||
### 12. No Other Modifications; Order of Precedence
|
||||
|
||||
Except as expressly provided herein, nothing in this Addendum shall be deemed to waive or modify any of the provisions of the Agreement, which otherwise remains in full force and effect. In the event of any conflict between the Agreement and this Addendum regarding the subject matter set forth herein, this Addendum shall prevail.
|
||||
|
||||
@@ -17,7 +17,7 @@ Capitalized terms used but not defined in these Acceptable Use Policies have the
|
||||
You are responsible for using the Service in compliance with all applicable laws, regulations, and all of our Acceptable Use Policies. These policies may be updated from time to time and are provided below, as well as in our [Terms of Service](/articles/github-terms-of-service) and [Corporate Terms of Service](/articles/github-corporate-terms-of-service).
|
||||
|
||||
### 2. Content Restrictions
|
||||
Under no circumstances will Users upload, post, host, execute, or transmit any Content to any repositories that:
|
||||
Under no circumstances will Users upload, post, host, execute, or transmit any Content that:
|
||||
|
||||
- is unlawful or promotes unlawful activities;
|
||||
|
||||
@@ -31,12 +31,14 @@ Under no circumstances will Users upload, post, host, execute, or transmit any C
|
||||
|
||||
- is or contains false, inaccurate, or intentionally deceptive information that is likely to adversely affect the public interest (including health, safety, election integrity, and civic participation);
|
||||
|
||||
- contains or installs any active malware or exploits, or uses our platform for exploit delivery (such as part of a command and control system);
|
||||
- directly supports [unlawful active attack or malware campaigns](/github/site-policy/github-community-guidelines#active-malware-or-exploits) that are causing technical harms — such as using our platform to deliver malicious executables or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers — with no implicit or explicit dual-use purpose prior to the abuse occurring; or
|
||||
|
||||
- shares unauthorized product licensing keys, software for generating unauthorized product licensing keys, or software for bypassing checks for product licensing keys, including extension of a free license beyond its trial period; or
|
||||
|
||||
- infringes any proprietary right of any party, including patent, trademark, trade secret, copyright, right of publicity, or other right.
|
||||
|
||||
Please see our [Community Guidelines](/github/site-policy/github-community-guidelines#what-is-not-allowed) for more details.
|
||||
|
||||
### 3. Conduct Restrictions
|
||||
While using the Service, under no circumstances will you:
|
||||
|
||||
|
||||
@@ -79,7 +79,20 @@ We are committed to maintaining a community where users are free to express them
|
||||
You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation) where such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to participate in public life. For example, we do not allow content that may put the well-being of groups of people at risk or limit their ability to take part in a free and open society. We encourage active participation in the expression of ideas, perspectives, and experiences and may not be in a position to dispute personal accounts or observations. We generally allow parody and satire that is in line with our Acceptable Use Polices, and we consider context to be important in how information is received and understood; therefore, it may be appropriate to clarify your intentions via disclaimers or other means, as well as the source(s) of your information.
|
||||
|
||||
- #### Active malware or exploits
|
||||
Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform for exploit delivery, such as using GitHub as a means to deliver malicious executables, or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Note, however, that we do not prohibit the posting of source code which could be used to develop malware or exploits, as the publication and distribution of such source code has educational value and provides a net benefit to the security community.
|
||||
Being part of a community includes not taking advantage of other members of the community. We do not allow anyone to use our platform in direct support of unlawful attacks that cause technical harms, such as using GitHub as a means to deliver malicious executables or as attack infrastructure, for example by organizing denial of service attacks or managing command and control servers. Technical harms means overconsumption of resources, physical damage, downtime, denial of service, or data loss, with no implicit or explicit dual-use purpose prior to the abuse occurring.
|
||||
|
||||
Note that GitHub allows dual use content and supports the posting of content that is used for research into vulnerabilities, malware, or exploits, as the publication and distribution of such content has educational value and provides a net benefit to the security community. We assume positive intention and use of these projects to promote and drive improvements across the ecosystem.
|
||||
|
||||
In rare cases of very widespread abuse of dual use content, we may restrict access to that specific instance of the content to disrupt an ongoing unlawful attack or malware campaign that is leveraging the GitHub platform as an exploit or malware CDN. In most of these instances, restriction takes the form of putting the content behind authentication, but may, as an option of last resort, involve disabling access or full removal where this is not possible (e.g. when posted as a gist). We will also contact the project owners about restrictions put in place where possible.
|
||||
|
||||
Restrictions are temporary where feasible, and do not serve the purpose of purging or restricting any specific dual use content, or copies of that content, from the platform in perpetuity. While we aim to make these rare cases of restriction a collaborative process with project owners, if you do feel your content was unduly restricted, we have an [appeals process](#appeal-and-reinstatement) in place.
|
||||
|
||||
To facilitate a path to abuse resolution with project maintainers themselves, prior to escalation to GitHub abuse reports, we recommend, but do not require, that repository owners take the following steps when posting potentially harmful security research content:
|
||||
|
||||
* Clearly identify and describe any potentially harmful content in a disclaimer in the project’s README.md file or source code comments.
|
||||
* Provide a preferred contact method for any 3rd party abuse inquiries through a SECURITY.md file in the repository (e.g. "Please create an issue on this repository for any questions or concerns"). Such a contact method allows 3rd parties to reach out to project maintainers directly and potentially resolve concerns without the need to file abuse reports.
|
||||
|
||||
*GitHub considers the npm registry to be a platform used primarily for installation and run-time use of code, and not for research.*
|
||||
|
||||
|
||||
### What happens if someone breaks the rules?
|
||||
@@ -95,6 +108,10 @@ Actions we may take in response to an abuse report include but are not limited t
|
||||
* Account Suspension
|
||||
* Account Termination
|
||||
|
||||
### Appeal and Reinstatement
|
||||
|
||||
In some cases there may be a basis to reverse an action, for example, based on additional information a user provided, or where a user has addressed the violation and agreed to abide by our Acceptable Use Policies moving forward. If you wish to appeal an enforcement action, please contact [support](https://support.github.com/contact).
|
||||
|
||||
### Legal Notices
|
||||
|
||||
We dedicate these Community Guidelines to the public domain for anyone to use, reuse, adapt, or whatever, under the terms of [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/).
|
||||
|
||||
@@ -6,16 +6,17 @@ topics:
|
||||
- Policy
|
||||
- Legal
|
||||
---
|
||||
#### What is this?
|
||||
|
||||
### What is this?
|
||||
From time to time, GitHub receives requests from governments to remove content that has been declared unlawful in their local jurisdiction. Although we may not always agree with those laws, we may need to block content if we receive a complete request from a government official so that our users in that jurisdiction may continue to have access to GitHub to collaborate and build software.
|
||||
|
||||
#### What is a complete government takedown request?
|
||||
### What is a complete government takedown request?
|
||||
To count as a complete request, a request or notice must
|
||||
- come from a relevant, official government agency
|
||||
- identify illegal content
|
||||
- specify the source of illegality in that jurisdiction (law or court order).
|
||||
|
||||
#### What happens when we receive a complete takedown request from a government?
|
||||
### What happens when we receive a complete takedown request from a government?
|
||||
|
||||
When we receive a notice from a relevant, official government agency that identifies illegal content and specifies the source of the illegality, we
|
||||
- notify the affected users of the specific content that allegedly violates the law, and that this is a legal takedown request
|
||||
@@ -23,11 +24,11 @@ When we receive a notice from a relevant, official government agency that identi
|
||||
- limit the geographic scope of the takedown when possible and include that as part of the notification
|
||||
- post the official request that led to the takedown in our public [gov-takedowns repository](https://github.com/github/gov-takedowns).
|
||||
|
||||
#### Why do we publicly post takedown notices?
|
||||
### Why do we publicly post takedown notices?
|
||||
We are concerned about Internet censorship, and believe that transparency on a specific and ongoing level is essential to good governance. By publicly posting the notices, we can better inform the public about what content is being withheld from GitHub, and why. We post takedown notices to document their potential to chill speech.
|
||||
|
||||
#### What does it mean if we post a notice in our gov-takedowns repository?
|
||||
### What does it mean if we post a notice in our gov-takedowns repository?
|
||||
It means that we received the notice on the indicated date. It does *not* mean that the content was unlawful or wrong. It does *not* mean that the user identified in the notice has done anything wrong. We don't make or imply any judgment about the merit of the claims they make. We post these notices and requests only for informational purposes.
|
||||
|
||||
#### Transparency reporting
|
||||
### Transparency reporting
|
||||
In addition to posting government takedown notices in our gov-takedowns repository, we report on them in our transparency report. We also track and report in our transparency report on government takedowns based on violations of GitHub's Terms of Service. We process those violations as we would process a Terms of Service violation reported by anyone else.
|
||||
|
||||
@@ -12,16 +12,16 @@ topics:
|
||||
|
||||
GitHub account names are available on a first-come, first-served basis, and are intended for immediate and active use.
|
||||
|
||||
#### What if the username I want is already taken?
|
||||
### What if the username I want is already taken?
|
||||
|
||||
Keep in mind that not all activity on GitHub is publicly visible; accounts with no visible activity may be in active use.
|
||||
|
||||
If the username you want has already been claimed, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you identify a desirable username still available.
|
||||
|
||||
#### Trademark Policy
|
||||
### Trademark Policy
|
||||
|
||||
If you believe someone's account is violating your trademark rights, you can find more information about making a trademark complaint on our [Trademark Policy](/articles/github-trademark-policy/) page.
|
||||
|
||||
#### Name Squatting Policy
|
||||
### Name Squatting Policy
|
||||
|
||||
GitHub prohibits account name squatting, and account names may not be reserved or inactively held for future use. Accounts violating this name squatting policy may be removed or renamed without notice. Attempts to sell, buy, or solicit other forms of payment in exchange for account names are prohibited and may result in permanent account suspension.
|
||||
|
||||
Reference in New Issue
Block a user