From 7cf8ee3088fb20c6aefeca87f8aaefa268666bd7 Mon Sep 17 00:00:00 2001 From: docs-bot <77750099+docs-bot@users.noreply.github.com> Date: Mon, 5 May 2025 21:59:30 -0700 Subject: [PATCH 1/4] Delete orphaned features (2025-05-05-16-29) (#55501) Co-authored-by: Sunbrye Ly <56200261+sunbrye@users.noreply.github.com> --- .../dependabot-updates-deprecate-rerun-failed-jobs.yml | 5 ----- 1 file changed, 5 deletions(-) delete mode 100644 data/features/dependabot-updates-deprecate-rerun-failed-jobs.yml diff --git a/data/features/dependabot-updates-deprecate-rerun-failed-jobs.yml b/data/features/dependabot-updates-deprecate-rerun-failed-jobs.yml deleted file mode 100644 index aee87a6a02a4..000000000000 --- a/data/features/dependabot-updates-deprecate-rerun-failed-jobs.yml +++ /dev/null @@ -1,5 +0,0 @@ -# Reference: Issue #3596 Deprecation: Changes to package manifests cause Dependabot to re-run failed jobs. -versions: - fpt: '*' - ghec: '*' - ghes: '>= 3.12' From 1e29bc9be7732c06abe99d11fca51153568657a8 Mon Sep 17 00:00:00 2001 From: jschnapper Date: Mon, 5 May 2025 22:01:20 -0700 Subject: [PATCH 2/4] Update push ruleset troubleshooting docs (#55491) --- .../managing-rulesets/troubleshooting-rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/troubleshooting-rules.md b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/troubleshooting-rules.md index cd07e6f96de3..07d1c2382485 100644 --- a/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/troubleshooting-rules.md +++ b/content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/troubleshooting-rules.md @@ -21,7 +21,7 @@ If a branch or tag is targeted by rules restricting the metadata of commits, you When utilizing push rulesets, a maximum of 1000 reference updates are allowed per push. If your push exceeds this limit, it will be rejected. For more information see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#creating-a-push-ruleset). -Additonally, push rulesets apply to the "Create a blob" and "Create or update file contents" endpoints in the REST API. See [AUTOTITLE](/rest/git/blobs?apiVersion=2022-11-28#create-a-blob) and [AUTOTITLE](/rest/repos/contents?apiVersion=2022-11-28#create-or-update-file-contents). +Additonally, push rulesets apply to the "Create a blob", "Create a tree", and "Create or update file contents" endpoints in the REST API. See [AUTOTITLE](/rest/git/blobs?apiVersion=2022-11-28#create-a-blob), [AUTOTITLE](/rest/git/trees?apiVersion=2022-11-28#create-a-tree), and [AUTOTITLE](/rest/repos/contents?apiVersion=2022-11-28#create-or-update-file-contents). ## Troubleshooting required status checks From 1092897588b6bd7cd9bdc105ec1b5ccc19e7d1e1 Mon Sep 17 00:00:00 2001 From: Jye Horan Date: Tue, 6 May 2025 13:28:40 +0800 Subject: [PATCH 3/4] Add auth headers to examples on best-practices-for-using-the-rest-api.md (#55509) --- .../best-practices-for-using-the-rest-api.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/rest/using-the-rest-api/best-practices-for-using-the-rest-api.md b/content/rest/using-the-rest-api/best-practices-for-using-the-rest-api.md index 725756e1e7a4..1df124505c14 100644 --- a/content/rest/using-the-rest-api/best-practices-for-using-the-rest-api.md +++ b/content/rest/using-the-rest-api/best-practices-for-using-the-rest-api.md @@ -69,18 +69,18 @@ Similarly, you should not try to manually construct pagination queries. Instead, ## Use conditional requests if appropriate -Most endpoints return an `etag` header, and many endpoints return a `last-modified` header. You can use the values of these headers to make conditional `GET` requests. If the response has not changed, you will receive a `304 Not Modified` response. Making a conditional request does not count against your primary rate limit if a `304` response is returned. +Most endpoints return an `etag` header, and many endpoints return a `last-modified` header. You can use the values of these headers to make conditional `GET` requests. If the response has not changed, you will receive a `304 Not Modified` response. Making a conditional request does not count against your primary rate limit if a `304` response is returned and the request was made while correctly authorized with an `Authorization` header. For example, if a previous request returned an `etag` header value of `644b5b0155e6404a9cc4bd9d8b1ae730`, you can use the `if-none-match` header in a future request: ```shell -curl {% data variables.product.rest_url %}/meta --include --header 'if-none-match: "644b5b0155e6404a9cc4bd9d8b1ae730"' +curl -H "Authorization: Bearer YOUR-TOKEN" {% data variables.product.rest_url %}/meta --include --header 'if-none-match: "644b5b0155e6404a9cc4bd9d8b1ae730"' ``` For example, if a previous request returned a `last-modified` header value of `Wed, 25 Oct 2023 19:17:59 GMT`, you can use the `if-modified-since` header in a future request: ```shell -curl {% data variables.product.rest_url %}/repos/github/docs --include --header 'if-modified-since: Wed, 25 Oct 2023 19:17:59 GMT' +curl -H "Authorization: Bearer YOUR-TOKEN" {% data variables.product.rest_url %}/repos/github/docs --include --header 'if-modified-since: Wed, 25 Oct 2023 19:17:59 GMT' ``` Conditional requests for unsafe methods, such as `POST`, `PUT`, `PATCH`, and `DELETE` are not supported unless otherwise noted in the documentation for a specific endpoint. From 4b9c2377a47f35645e2b0f8976d4687b86c32978 Mon Sep 17 00:00:00 2001 From: Mike Cherry Date: Tue, 6 May 2025 00:52:01 -0500 Subject: [PATCH 4/4] Update configuring-built-in-firewall-rules.md (#55499) Co-authored-by: Sunbrye Ly <56200261+sunbrye@users.noreply.github.com> --- .../configuring-built-in-firewall-rules.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/content/admin/configuring-settings/configuring-network-settings/configuring-built-in-firewall-rules.md b/content/admin/configuring-settings/configuring-network-settings/configuring-built-in-firewall-rules.md index 7dd5089ec3b5..537b984b31b8 100644 --- a/content/admin/configuring-settings/configuring-network-settings/configuring-built-in-firewall-rules.md +++ b/content/admin/configuring-settings/configuring-network-settings/configuring-built-in-firewall-rules.md @@ -78,6 +78,9 @@ We do not recommend customizing UFW as it can complicate some troubleshooting is sudo cp -r /etc/ufw ~/ufw.backup ``` +> [!WARNING] +> If you're upgrading your server with an upgrade package you will need to back up your firewall rules to a remote location before installing the upgrade. When using an upgrade package, the root partition is replaced and any custom files that were created will be lost. This doesn’t happen when you upgrade your server using a hotpatch. + After you upgrade {% data variables.location.product_location %}, you must reapply your custom firewall rules. We recommend that you create a script to reapply your firewall custom rules. ## Restoring the default firewall rules @@ -86,6 +89,8 @@ If something goes wrong after you change the firewall rules, you can reset the r > [!WARNING] > If you didn't back up the original rules before making changes to the firewall, visit {% data variables.contact.contact_ent_support %} and contact us for further assistance. +> +> If you backed up your original rules to a remote location prior to an upgrade, they will need to be transferred back to your server before they can be restored. {% data reusables.enterprise_installation.ssh-into-instance %}