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: content/actions/reference/limits.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -83,3 +83,9 @@ When using larger runners with vnet injection, you need to determine the appropr
83
83
***OAuth apps \-** {% data reusables.rest-api.primary-rate-limit-oauth-apps %}
84
84
***GITHUB TOKEN**\- {% data reusables.rest-api.primary-rate-limit-github-token-in-actions %}
85
85
***Secondary rate limits**\- In addition to primary rate limits, {% data variables.product.github %} enforces secondary rate limits in order to prevent abuse and keep the API available for all users, these are not configurable with GHEC. For more information, see [AUTOTITLE](/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28#about-secondary-rate-limits).
86
+
87
+
### Docker Hub's rate limit for {% data variables.product.prodname_actions %}
88
+
89
+
***{% data variables.product.github %}-hosted runners pulling public images:** Docker Hub's rate limit is not applied.
90
+
***{% data variables.product.github %}-hosted runners pulling private images:** Pulling private images from Docker Hub is subject to the rate limit.
91
+
***Self-hosted runners pulling public or private images:** Pulling images from Docker Hub is always subject to the rate limit.
Copy file name to clipboardExpand all lines: content/code-security/secret-scanning/introduction/about-secret-scanning-for-partners.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,10 @@ shortTitle: Secret scanning for partners
18
18
19
19
> [!NOTE]You cannot change the configuration of {% data variables.product.prodname_secret_scanning %} for partner patterns on public repositories.
20
20
21
+
{% data variables.secret-scanning.partner_alerts_caps %} scans:
22
+
23
+
{% data reusables.secret-scanning.what-is-scanned %}
24
+
21
25
The reason partner alerts are directly sent to the secret providers whenever a leak is detected for one of their secrets is that this enables the provider to take immediate action to protect you and protect their resources. The notification process for regular alerts is different. Regular alerts are displayed on the repository's **Security** tab on {% data variables.product.prodname_dotcom %} for you to resolve.
22
26
23
27
{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
Copy file name to clipboardExpand all lines: content/code-security/secret-scanning/introduction/about-secret-scanning.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,8 +29,14 @@ shortTitle: Secret scanning
29
29
30
30
{% data variables.product.prodname_secret_scanning_caps %} scans your entire Git history on all branches present in your {% data variables.product.prodname_dotcom %} repository for secrets, even if the repository is archived. {% data variables.product.prodname_dotcom %} will also periodically run a full Git history scan for new secret types in existing content in {% ifversion fpt or ghec %}public repositories{% else %}repositories with {% data variables.product.prodname_GH_secret_protection %} enabled{% endif %} where {% data variables.product.prodname_secret_scanning %} is enabled when new supported secret types are added.
31
31
32
+
Additionally, {% data variables.product.prodname_secret_scanning %} scans:
33
+
32
34
{% data reusables.secret-scanning.what-is-scanned %}
33
35
36
+
{% ifversion fpt or ghec %}
37
+
This additional scanning is free for public repositories.
> Regardless of the enablement status of {% data variables.product.prodname_AS %} features, organizations on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %} can run a free report to scan the code in the organization for leaked secrets.
Copy file name to clipboardExpand all lines: content/copilot/concepts/tools/ai-tools.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ The use of AI tools is increasingly becoming a standard part of a software devel
37
37
***Deployment**:
38
38
***{% data variables.copilot.copilot_chat_short %}** can help you configure continuous integration and continuous deployment (CI/CD) pipelines.
39
39
***Operation**:
40
-
***{% data variables.copilot.copilot_coding_agent %}**({% data variables.release-phases.public_preview %}) can raise pull requests for open issues.
40
+
***{% data variables.copilot.copilot_coding_agent %}** can raise pull requests for open issues.
41
41
***{% data variables.copilot.copilot_chat_short %}** can help with tasks you're working on yourself.
42
42
43
43
## Planning
@@ -125,7 +125,7 @@ The deployment phase involves preparing your code for production and ensuring a
125
125
126
126
During the operation phase, the focus is on maintaining and monitoring your application in production to ensure it runs smoothly and meets user expectations. This phase often involves tasks like debugging production issues, optimizing performance, and ensuring system reliability.
127
127
128
-
You can use the **{% data variables.copilot.copilot_coding_agent %}**({% data variables.release-phases.public_preview %}) as an autonomous agent that can help maintain and improve your application in production. Assign a {% data variables.product.github %} issue to {% data variables.product.prodname_copilot_short %}, and it will autonomously explore the repository, identify potential fixes, and create a pull request with the proposed changes. Then it will automatically request a review from you.
128
+
You can use the **{% data variables.copilot.copilot_coding_agent %}** as an autonomous agent that can help maintain and improve your application in production. Assign a {% data variables.product.github %} issue to {% data variables.product.prodname_copilot_short %}, and it will autonomously explore the repository, identify potential fixes, and create a pull request with the proposed changes. Then it will automatically request a review from you.
129
129
130
130
For issues you're tackling yourself, use **{% data variables.copilot.copilot_chat_short %}** for help analyzing logs, debugging issues, and suggesting optimizations. For example:
| {% data variables.copilot.copilot_code-review_short %} |[AUTOTITLE](/copilot/how-tos/agents/copilot-code-review/automatic-code-review)|
160
160
| {% data variables.copilot.copilot_custom_agents %} |[AUTOTITLE](/copilot/concepts/agents/coding-agent/about-custom-agents)|
161
-
| {% data variables.copilot.copilot_coding_agent %} ({% data variables.release-phases.public_preview %}) |[AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/enabling-developers/using-copilot-coding-agent-in-org)|
161
+
| {% data variables.copilot.copilot_coding_agent %} |[AUTOTITLE](/copilot/rolling-out-github-copilot-at-scale/enabling-developers/using-copilot-coding-agent-in-org)|
162
162
| {% data variables.copilot.copilot_autofix_short %} |[AUTOTITLE](/code-security/code-scanning/enabling-code-scanning/configuring-default-setup-for-code-scanning)|
Copy file name to clipboardExpand all lines: content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,8 @@ Gists can be public or secret. Public gists show up in {% data variables.gists.d
22
22
23
23
Secret gists don't show up in {% data variables.gists.discover_url %} and are not searchable unless you are logged in and are the author of the secret gist. Secret gists aren't private. If you send the URL of a secret gist to a friend, they'll be able to see it. However, if someone you don't know discovers the URL, they'll also be able to see your gist. If you need to keep your code away from prying eyes, you may want to [create a private repository](/repositories/creating-and-managing-repositories/creating-a-new-repository) instead.
24
24
25
+
For {% data variables.product.prodname_dotcom_the_website %} and {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.github %} automatically scans _secret gists_ for partner secrets and informs the relevant partner whenever one of their secrets is leaked.{% ifversion fpt or ghec %} See [AUTOTITLE](/code-security/secret-scanning/introduction/about-secret-scanning-for-partners).{% endif %}
26
+
25
27
{% data reusables.gist.cannot-convert-public-gists-to-secret %} However, a secret gist can be made public by editing the gist and updating the visibility to public.
Additionally, {% data variables.product.prodname_secret_scanning %} scans:
2
1
* Descriptions and comments in issues
3
2
* Titles, descriptions, and comments, in open and closed _historical_ issues{% ifversion fpt or ghec %}. A notification is sent to the relevant partner when a historical partner pattern is detected.{% endif %}
4
3
* Titles, descriptions, and comments in pull requests
5
4
* Titles, descriptions, and comments in {% data variables.product.prodname_discussions %}{% ifversion secret-scanning-enhancements-wikis %}
6
5
* Wikis{% endif %}
7
-
8
-
{% ifversion fpt or ghec %}
9
-
This additional scanning is free for public repositories.
10
-
{% endif %}
6
+
* Secret gists. A notification is sent to the relevant partner when a partner pattern is detected in a secret gist.
11
7
12
8
{% data reusables.secret-scanning.beta-prs-discussions-wikis-scanned %}
0 commit comments