Skip to content

Commit 52e3f63

Browse files
authored
Merge pull request #36035 from github/repo-sync
Repo sync
2 parents c33ff48 + d0e866e commit 52e3f63

File tree

8 files changed

+29
-2
lines changed

8 files changed

+29
-2
lines changed

Diff for: content/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ The following rules apply to secret names:
4040

4141
{% data reusables.codespaces.secret-precedence %} Similarly, if an organization, repository, and environment all have a secret with the same name, the environment-level secret takes precedence.
4242

43-
To help ensure that {% data variables.product.prodname_dotcom %} redacts your secret in logs, avoid using structured data as the values of secrets. For example, avoid creating secrets that contain JSON or encoded Git blobs.
43+
To help ensure that {% data variables.product.prodname_dotcom %} redacts your secrets in logs correctly, avoid using structured data as the values of secrets. For example, avoid creating secrets that contain JSON or encoded Git blobs. Using structured data as secrets could cause non-secrets to be detected as such, making passing data between workflows harder to implement. In such cases, consider manipulating the structured data, for example encoding them to a string, before storing them as secrets, and decoding them before they are used.
4444

4545
### Accessing your secrets
4646

Diff for: content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md

+7
Original file line numberDiff line numberDiff line change
@@ -113,6 +113,13 @@ If your instance has subdomain isolation disabled:
113113

114114
## Publishing a package
115115

116+
{% ifversion packages-nuget-v2 %}
117+
118+
> [!NOTE]
119+
> The `nupkg` archive for a NuGet package version must be smaller than 2.147 GB in size.
120+
121+
{% endif %}
122+
116123
You can publish a package to {% data variables.product.prodname_registry %} by authenticating with a _nuget.config_ file, using the `--api-key` command line option with your {% data variables.product.prodname_dotcom %} {% data variables.product.pat_v1 %} or by using command that can be run directly from the command line using the `dotnet` command-line interface (CLI).
117124

118125
Replace `OWNER` with your username or company name, and `YOUR_GITHUB_PAT` with your {% data variables.product.pat_generic %}.

Diff for: content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md

+4
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,8 @@ You are responsible for using the Service in compliance with all applicable laws
2222

2323
We do not allow content or activity on GitHub that:
2424

25+
<!-- markdownlint-disable GHD034 -->
26+
2527
* is unlawful or promotes unlawful activities;
2628

2729
* 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:
7476
* 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
7577
* 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.
7678

79+
<!-- markdownlint-enable GHD034 -->
80+
7781
## 6. Services Usage Limits
7882

7983
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.

Diff for: content/site-policy/github-company-policies/github-anti-bribery-statement.md

+4
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,8 @@ GitHub’s **Gifts and Entertainment Policy** explains that bribery is not permi
3434

3535
## Training for our employees
3636

37+
<!-- markdownlint-disable GHD034 -->
38+
3739
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,
3840
* definition and structural effects of corruption
3941
* who is covered, including
@@ -49,6 +51,8 @@ GitHub employees are required to participate in training on corruption, includin
4951
* due diligence and red flags
5052
* record-keeping requirements
5153

54+
<!-- markdownlint-enable GHD034 -->
55+
5256
In addition, the training covers GitHub’s internal policies related to anti-corruption and bribery, including our non-retaliation (whistleblower) policy.
5357

5458
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.

Diff for: content/site-policy/github-terms/github-terms-of-service.md

+4
Original file line numberDiff line numberDiff line change
@@ -316,6 +316,8 @@ GitHub does not warrant that the Service will meet your requirements; that the S
316316

317317
You understand and agree that we will not be liable to you or any third party for any loss of profits, use, goodwill, or data, or for any incidental, indirect, special, consequential or exemplary damages, however arising, that result from
318318

319+
<!-- markdownlint-disable GHD034 -->
320+
319321
* the use, disclosure, or display of your User-Generated Content;
320322
* your use or inability to use the Service;
321323
* any modification, price change, suspension or discontinuance of the Service;
@@ -325,6 +327,8 @@ You understand and agree that we will not be liable to you or any third party fo
325327
* any other user interactions that you input or receive through your use of the Service; or
326328
* any other matter relating to the Service.
327329

330+
<!-- markdownlint-enable GHD034 -->
331+
328332
Our liability is limited whether or not we have been informed of the possibility of such damages, and even if a remedy set forth in this Agreement is found to have failed of its essential purpose. We will have no liability for any failure or delay due to matters beyond our reasonable control.
329333

330334
## P. Release and Indemnification

Diff for: content/site-policy/other-site-policies/github-government-takedown-policy.md

+4
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ From time to time, GitHub receives requests from governments to remove content t
1616

1717
## What is a complete government takedown request?
1818

19+
<!-- markdownlint-disable GHD034 -->
20+
1921
To count as a complete request, a request or notice must
2022
* come from a relevant, official government agency
2123
* identify illegal content
@@ -29,6 +31,8 @@ When we receive a notice from a relevant, official government agency that identi
2931
* limit the geographic scope of the takedown when possible and include that as part of the notification
3032
* post the official request that led to the takedown in our public [gov-takedowns repository](https://github.com/github/gov-takedowns).
3133

34+
<!-- markdownlint-enable GHD034 -->
35+
3236
## Why do we publicly post takedown notices?
3337

3438
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.

Diff for: content/site-policy/privacy-policies/github-general-privacy-statement.md

+4
Original file line numberDiff line numberDiff line change
@@ -108,12 +108,16 @@ We may share Personal Data with the following recipients:
108108

109109
If your GitHub account has private repositories, you control the access to that information. GitHub personnel does not access private repository information without your consent except as provided in this Privacy Statement and for:
110110

111+
<!-- markdownlint-disable GHD034 -->
112+
111113
* security purposes
112114
* automated scanning or manual review for known vulnerabilities, active malware, or other content known to violate our Terms of Service
113115
* to assist the repository owner with a support matter
114116
* to maintain the integrity of the Services, or
115117
* to comply with our legal obligations if we have reason to believe the contents are in violation of the law.
116118

119+
<!-- markdownlint-enable GHD034 -->
120+
117121
GitHub will provide you with notice regarding private repository access unless doing so is prohibited by law or if GitHub acted in response to a security threat or other risk to security.
118122

119123
## Lawful Bases for Processing Personal Data (Applicable to EEA and UK End Users)

Diff for: content/site-policy/security-policies/github-sirt-description-rfc-2350.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ Some examples of GitHub products and services are:
134134
* GitHub Desktop
135135
* GitHub CLI
136136
* GitHub API
137-
* npm
137+
* npm <!-- markdownlint-disable-line GHD034 -->
138138

139139
### 3.3 Sponsorship and/or Affiliation
140140

0 commit comments

Comments
 (0)