diff --git a/data/release-notes/enterprise-server/3-7/1.yml b/data/release-notes/enterprise-server/3-7/1.yml
index e9e4a00cb13e..0718ba0626cf 100644
--- a/data/release-notes/enterprise-server/3-7/1.yml
+++ b/data/release-notes/enterprise-server/3-7/1.yml
@@ -37,25 +37,6 @@ sections:
     - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
     - In some cases, users cannot convert existing issues to discussions.
     - During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
-    - |
-      In some cases after upgrading to GitHub Enterprise Server 3.7.0, users may encounter `Internal Server Error` or `500` errors when initiating `git` operations over SSH or HTTPS. Example:
-
-        ```
-        git push origin master
-        Total 0 (delta 0), reused 0 (delta 0)
-        remote: Internal Server Error
-        To ghes.hostname.com:User/repo.git
-        ! [remote rejected]       master -> master (Internal Server Error)
-        ```
-      
-      If these are encountered, please [contact GitHub Enterprise Support](/support/contacting-github-support/creating-a-support-ticket) with a support bundle. The known temporary workaround at this time is to restart the `github-gitauth` service with the commands below:
-
-        ```
-        nomad stop github-gitauth
-        nomad run /etc/nomad-jobs/github/gitauth.hcl
-        nomad status git
-        ```
-      We are currently investigating a permanent fix for a future hot patch.
 
   deprecations:
     # https://github.com/github/enterprise-releases/issues/3217