You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Policies/acceptable-use-policies/github-acceptable-use-policies.md
+5-1Lines changed: 5 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,8 @@ You are responsible for using the Service in compliance with all applicable laws
22
22
23
23
We do not allow content or activity on GitHub that:
24
24
25
+
<!-- markdownlint-disable GHD034 -->
26
+
25
27
* is unlawful or promotes unlawful activities;
26
28
27
29
* is [sexually obscene](/site-policy/acceptable-use-policies/github-sexually-obscene-content) or relates to sexual exploitation or abuse, including of minors;
@@ -74,6 +76,8 @@ We do not allow content or activity on GitHub that:
74
76
* directly supports [unlawful active attack or malware campaigns](/site-policy/acceptable-use-policies/github-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
75
77
* uses our servers to disrupt or to attempt to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account or network. Please note, activities permitted under bug bounty programs, such as the [GitHub Bug Bounty program](https://bounty.github.com), are not considered “unauthorized,” but must only affect the organization whose bug bounty program authorized the activity.
76
78
79
+
<!-- markdownlint-enable GHD034 -->
80
+
77
81
## 6. Services Usage Limits
78
82
79
83
You will not reproduce, duplicate, copy, sell, resell or exploit any portion of the Service, use of the Service, or access to the Service without our express written permission.
@@ -99,7 +103,7 @@ Any person, entity, or service collecting data from the Service must comply with
99
103
100
104
## 9. Excessive Bandwidth Use
101
105
102
-
The Service's bandwidth limitations vary based on the features you use. If we determine your bandwidth usage to be significantly excessive in relation to other users of similar features, we reserve the right to suspend your Account, throttle your file hosting, or otherwise limit your activity until you can reduce your bandwidth consumption. We also reserve the right—after providing advance notice—to delete repositories that we determine to be placing undue strain on our infrastructure. For guidance on acceptable use of object storage in repositories, refer to "[AUTOTITLE](/repositories/working-with-files/managing-large-files/about-large-files-on-github)". For more details on specific features' bandwidth limitations, see the [GitHub Additional Product Terms](/site-policy/github-terms/github-terms-for-additional-products-and-features).
106
+
The Service's bandwidth limitations vary based on the features you use. If we determine your bandwidth usage to be significantly excessive in relation to other users of similar features, we reserve the right to suspend your Account, throttle your file hosting, or otherwise limit your activity until you can reduce your bandwidth consumption. We also reserve the right—after providing advance notice—to delete repositories that we determine to be placing undue strain on our infrastructure. For guidance on acceptable use of object storage in repositories, refer to [AUTOTITLE](/repositories/working-with-files/managing-large-files/about-large-files-on-github). For more details on specific features' bandwidth limitations, see the [GitHub Additional Product Terms](/site-policy/github-terms/github-terms-for-additional-products-and-features).
Copy file name to clipboardExpand all lines: Policies/content-removal-policies/dmca-takedown-policy.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ topics:
16
16
17
17
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.
18
18
19
-
(If you just want to submit a notice, you can skip to "[G. Submitting Notices](#g-submitting-notices).")
19
+
(If you just want to submit a notice, you can skip to [G. Submitting Notices](#g-submitting-notices).)
20
20
21
21
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.
22
22
@@ -65,7 +65,7 @@ Here are the basic steps in the process.
65
65
66
66
## B. What About Forks? (or What's a Fork?)
67
67
68
-
One of the best features of GitHub is the ability for users to "fork" one another's repositories. What does that mean? In essence, it means that users can make a copy of a project on GitHub into their own repositories. As the license or the law allows, users can then make changes to that fork to either push back to the main project or just keep as their own variation of a project. Each of these copies is a "[AUTOTITLE](/get-started/learning-about-github/github-glossary#fork)" of the original repository, which in turn may also be called the "parent" of the fork.
68
+
One of the best features of GitHub is the ability for users to "fork" one another's repositories. What does that mean? In essence, it means that users can make a copy of a project on GitHub into their own repositories. As the license or the law allows, users can then make changes to that fork to either push back to the main project or just keep as their own variation of a project. Each of these copies is a [AUTOTITLE](/get-started/learning-about-github/github-glossary#fork) of the original repository, which in turn may also be called the "parent" of the fork.
69
69
70
70
GitHub _will not_ automatically disable forks when disabling a parent repository. This is because forks belong to different users, may have been altered in significant ways, and may be licensed or used in a different way that is protected by the fair-use doctrine. GitHub does not conduct any independent investigation into forks. We expect copyright owners to conduct that investigation and, if they believe that the forks are also infringing, expressly include forks in their takedown notice.
71
71
@@ -82,7 +82,7 @@ A circumvention claim must include the following details about the technical mea
82
82
83
83
GitHub will review circumvention claims closely, including by both technical and legal experts. In the technical review, we will seek to validate the details about the manner in which the technical protection measures operate and the way the project allegedly circumvents them. In the legal review, we will seek to ensure that the claims do not extend beyond the boundaries of the DMCA. In cases where we are unable to determine whether a claim is valid, we will err on the side of the developer, and leave the content up. If the claimant wishes to follow up with additional detail, we would start the review process again to evaluate the revised claims.
84
84
85
-
Where our experts determine that a claim is complete, legal, and technically legitimate, we will contact the repository owner and give them a chance to respond to the claim or make changes to the repo to avoid a takedown. If they do not respond, we will attempt to contact the repository owner again before taking any further steps. In other words, we will not disable a repository based on a claim of circumvention technology without attempting to contact a repository owner to give them a chance to respond or make changes first. If we are unable to resolve the issue by reaching out to the repository owner first, we will always be happy to consider a response from the repository owner even after the content has been disabled if they would like an opportunity to dispute the claim, present us with additional facts, or make changes to have the content restored. When we need to disable content, we will ensure that repository owners can export their issues and pull requests and other repository data that do not contain the alleged circumvention code to the extent legally possible.
85
+
Where our experts determine that a claim is complete, legal, and technically legitimate, we will contact the repository owner and give them a chance to respond to the claim or make changes to the repo to avoid a takedown. If they do not respond, we will attempt to contact the repository owner again before taking any further steps. In other words, we will not disable a repository based on a claim of circumvention technology without attempting to contact a repository owner to give them a chance to respond or make changes first. If we are unable to resolve the issue by reaching out to the repository owner first, we will always be happy to consider a response from the repository owner even after the content has been disabled if they would like an opportunity to dispute the claim, present us with additional facts, or make changes to have the content restored. When we need to disable content, we will ensure that repository owners can export their issues and pull requests and other repository data that do not contain the alleged circumvention code to the extent legally possible.
86
86
87
87
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.
Copy file name to clipboardExpand all lines: Policies/content-removal-policies/github-private-information-removal-policy.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ For the purposes of this document, “private information” refers to content t
66
66
67
67
### What About Forks? (or What's a Fork?)
68
68
69
-
One of the best features of GitHub is the ability for users to "fork" one another's repositories. What does that mean? In essence, it means that users can make a copy of a project on GitHub into their own repositories. As the license or the law allows, users can then make changes to that fork to either push back to the main project or just keep as their own variation of a project. Each of these copies is a "[AUTOTITLE](/get-started/learning-about-github/github-glossary#fork)" of the original repository, which in turn may also be called the "parent" of the fork.
69
+
One of the best features of GitHub is the ability for users to "fork" one another's repositories. What does that mean? In essence, it means that users can make a copy of a project on GitHub into their own repositories. As the license or the law allows, users can then make changes to that fork to either push back to the main project or just keep as their own variation of a project. Each of these copies is a [AUTOTITLE](/get-started/learning-about-github/github-glossary#fork) of the original repository, which in turn may also be called the "parent" of the fork.
70
70
71
71
GitHub will not automatically disable forks when disabling a parent repository. This is because forks belong to different users and may have been altered in significant ways. GitHub does not conduct any independent investigation into forks. We expect those sending private information removal requests to conduct that investigation and, if they believe that the forks also contain private information, expressly include forks in their request.
Copy file name to clipboardExpand all lines: Policies/github-company-policies/github-anti-bribery-statement.md
+5-1Lines changed: 5 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ topics:
9
9
- Policy
10
10
- Legal
11
11
---
12
-
GitHub upholds our commitment to ethical business practices, including by prohibiting bribery and corruption. As [Transparency International](https://www.transparency.org/what-is-corruption#costs-of-corruption) explains, the costs of corruption are
12
+
GitHub upholds our commitment to ethical business practices, including by prohibiting bribery and corruption. As [Transparency International](https://www.transparency.org/what-is-corruption) explains, the costs of corruption are
13
13
***political**, by posing a major obstacle to democracy and the rule of law
14
14
***economic**, by depleting national wealth
15
15
***social**, by undermining people’s trust in political society, institutions, and leaders
@@ -34,6 +34,8 @@ GitHub’s **Gifts and Entertainment Policy** explains that bribery is not permi
34
34
35
35
## Training for our employees
36
36
37
+
<!-- markdownlint-disable GHD034 -->
38
+
37
39
GitHub employees are required to participate in training on corruption, including bribery. We also provide additional training for particularly relevant people and teams, such as our sales team. The training explains relevant elements of the U.S. Foreign Corrupt Practices Act and the U.K. Bribery Act of 2010. For example,
38
40
* definition and structural effects of corruption
39
41
* who is covered, including
@@ -49,6 +51,8 @@ GitHub employees are required to participate in training on corruption, includin
49
51
* due diligence and red flags
50
52
* record-keeping requirements
51
53
54
+
<!-- markdownlint-enable GHD034 -->
55
+
52
56
In addition, the training covers GitHub’s internal policies related to anti-corruption and bribery, including our non-retaliation (whistleblower) policy.
53
57
54
58
While the U.S. FCPA is focused on interactions with government officials, the U.K. Bribery Act is broader and extends to bribing anyone, regardless of whether they are a government official. Both laws can extend to GitHub’s actions elsewhere on the globe. GitHub’s policies prohibit bribing anyone, anywhere in the world.
Copy file name to clipboardExpand all lines: Policies/github-company-policies/github-statement-against-modern-slavery-and-child-labor.md
+13-13Lines changed: 13 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ topics:
11
11
---
12
12
_2018 statement_
13
13
14
-
According to the International Labour Organization (ILO), [40 million people were victims of modern slavery and 152 million children were subject to child labor](https://www.ilo.org/global/about-the-ilo/newsroom/news/WCMS_574717/lang--en/index.htm) globally in 2016. As the [ILO reports](https://www.ilo.org/global/topics/forced-labour/lang--en/index.htm):
14
+
According to the International Labour Organization (ILO), [40 million people were victims of modern slavery and 152 million children were subject to child labor](https://www.ilo.org/global/about-the-ilo/newsroom/news/WCMS_574717/lang--en/index.htm) globally in 2016. As the [ILO reports](https://www.ilo.org/topics-and-sectors/forced-labour-modern-slavery-and-trafficking-persons):
15
15
* 1 in 4 victims of modern slavery are children.
16
16
* Out of the 24.9 million people trapped in forced labour, 16 million people are exploited in the private sector such as domestic work, construction or agriculture; 4.8 million persons in forced sexual exploitation, and 4 million persons in forced labour imposed by state authorities.
17
17
* Women and girls are disproportionately affected by forced labour, accounting for 99% of victims in the commercial sex industry, and 58% in other sectors.
@@ -56,19 +56,19 @@ GitHub has a non-retaliation policy for reporting workplace-related concerns. Co
56
56
57
57
GitHub's labor practices are
58
58
59
-
**fair**:
59
+
**fair:**
60
60
* GitHub pays its employees and contractors a fair wage, in accordance with applicable legal wages
61
61
* GitHub maintains humane working conditions
62
62
* GitHub does not require workers to exceed the maximum hours of daily labor set by local and national laws or regulations
63
63
* GitHub pays its employees and contractors in a timely manner, with documentation (such as a pay stub) stating the basis on which they are paid, and keeps employee records in accordance with local and national laws
64
64
65
-
**humane and ethical**:
65
+
**humane and ethical:**
66
66
* GitHub uses only voluntary labor
67
67
* GitHub prohibits child labor
68
68
* GitHub does not engage in physical discipline or abuse
69
69
* GitHub does not tolerate harassment or unlawful discrimination in the workforce or workplace
70
70
71
-
**respectful**:
71
+
**respectful:**
72
72
* GitHub protects its employees' rights to freedom of association and collective bargaining in accordance with legal requirements, including to post legal notices of employees' rights under the National Labor Relations Act
73
73
* GitHub provides benefits to employees at or in excess of levels expected in the industry
74
74
* GitHub encourages employees to report any workplace complaint and does not tolerate retaliation for reporting
@@ -88,17 +88,17 @@ Although GitHub knows of no actual or alleged modern slavery or child labor in i
88
88
GitHub complies and will continue to comply with laws related to modern slavery and child labor.
89
89
90
90
Going forward, GitHub now requires its suppliers to comply with this Statement, as well as laws related to modern slavery and child labor. GitHub now also requires its suppliers to:
91
-
*not use, participate in, support, or tolerate modern slavery or child labor
92
-
*not use misleading or fraudulent recruitment or engagement practices for employees or contract workers
93
-
*not charge employees or contract workers recruitment or engagement fees
94
-
*not destroy, conceal, confiscate, or otherwise deny access by an employee or any contract worker to passport, driver's license, or other identity documents;
95
-
*allow us to terminate our agreements with them for any violation of its obligations related to modern slavery or child labor; and
96
-
*remediate any harms caused to any worker found to be subjected to any form of modern slavery or child labor, if required by law.
91
+
*Not use, participate in, support, or tolerate modern slavery or child labor
92
+
*Not use misleading or fraudulent recruitment or engagement practices for employees or contract workers
93
+
*Not charge employees or contract workers recruitment or engagement fees
94
+
*Not destroy, conceal, confiscate, or otherwise deny access by an employee or any contract worker to passport, driver's license, or other identity documents;
95
+
*Allow us to terminate our agreements with them for any violation of its obligations related to modern slavery or child labor; and
96
+
*Remediate any harms caused to any worker found to be subjected to any form of modern slavery or child labor, if required by law.
97
97
98
98
In addition, GitHub strongly encourages its suppliers to:
99
-
*conduct anti-modern slavery and child labor due diligence processes, including risk assessments, for their suppliers;
100
-
*take steps to address risks identified; and
101
-
*use similar anti-modern slavery and child labor language with their suppliers.
99
+
*Conduct anti-modern slavery and child labor due diligence processes, including risk assessments, for their suppliers;
100
+
*Take steps to address risks identified; and
101
+
*Use similar anti-modern slavery and child labor language with their suppliers.
102
102
103
103
GitHub's procurement instructions to employees making company purchases now includes a reference to the requirement for suppliers to comply with Microsoft's Supplier Code of Conduct or this Statement.
Copy file name to clipboardExpand all lines: Policies/github-terms/github-community-code-of-conduct.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -99,7 +99,7 @@ The community is here for users to build trust through authentic reputations. No
99
99
100
100
***If you see a problem, report it.** Moderators have special authority; they are responsible for this GitHub Community. But so are you. With your help, moderators can be community facilitators, not just janitors or police.
101
101
102
-
When you see bad behavior, don’t reply. It encourages the bad behavior by acknowledging it, consumes your energy, and wastes everyone’s time. You can report a disruptive user or disruptive content to GitHub. For more information, see "[AUTOTITLE](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)."
102
+
When you see bad behavior, don’t reply. It encourages the bad behavior by acknowledging it, consumes your energy, and wastes everyone’s time. You can report a disruptive user or disruptive content to GitHub. For more information, see [AUTOTITLE](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).
0 commit comments