mgravell · Nov 9, 2026 · Nov 9, 2026
diff --git a/Directory.Build.props b/Directory.Build.props
@@ -17,7 +17,7 @@
 
     <LangVersion>14</LangVersion>
     <RepositoryType>git</RepositoryType>
-    <RepositoryUrl>https://github.com/StackExchange/StackExchange.Redis/</RepositoryUrl>
+    <RepositoryUrl>https://github.com/seredis/StackExchange.Redis/</RepositoryUrl>
 
     <DebugSymbols>true</DebugSymbols>
     <DebugType>embedded</DebugType>

diff --git a/README.md b/README.md
@@ -7,7 +7,7 @@ For all documentation, [see here](https://stackexchange.github.io/StackExchange.
 
 #### Build Status
 
-[![CI](https://github.com/StackExchange/StackExchange.Redis/actions/workflows/CI.yml/badge.svg)](https://github.com/StackExchange/StackExchange.Redis/actions/workflows/CI.yml)
+[![CI](https://github.com/seredis/StackExchange.Redis/actions/workflows/CI.yml/badge.svg)](https://github.com/seredis/StackExchange.Redis/actions/workflows/CI.yml)
 
 #### Package Status
 

diff --git a/docs/ReleaseNotes.md b/docs/ReleaseNotes.md
diff --git a/docs/RespLogging.md b/docs/RespLogging.md
@@ -106,7 +106,7 @@ If the RESP streams are *not* valid, an exception will provide further details.
 **An exception here is strong evidence that there is a fault either in the redis server, or an intermediate proxy**.
 
 Conversely, if the library reported a protocol failure but the validation step here *does not* report an error, then
-that is strong evidence of a library error; [**please report this**](https://github.com/StackExchange/StackExchange.Redis/issues/new) (with details).
+that is strong evidence of a library error; [**please report this**](https://github.com/seredis/StackExchange.Redis/issues/new) (with details).
 
 You can also *replay* the conversation locally, seeing the individual requests and responses:
 

diff --git a/docs/ServerMaintenanceEvent.md b/docs/ServerMaintenanceEvent.md
@@ -28,7 +28,7 @@ multiplexer.ServerMaintenanceEvent += (object sender, ServerMaintenanceEvent e)
     }
 };
 ```
-You can see the schema for the `AzureMaintenanceEvent` class [here](https://github.com/StackExchange/StackExchange.Redis/blob/main/src/StackExchange.Redis/Maintenance/AzureMaintenanceEvent.cs). Note that the library automatically sets the `ReceivedTimeUtc` timestamp when the event is received, so if you see in your logs that `ReceivedTimeUtc` is after `StartTimeUtc`, this may indicate that your connections are under high load.
+You can see the schema for the `AzureMaintenanceEvent` class [here](https://github.com/seredis/StackExchange.Redis/blob/main/src/StackExchange.Redis/Maintenance/AzureMaintenanceEvent.cs). Note that the library automatically sets the `ReceivedTimeUtc` timestamp when the event is received, so if you see in your logs that `ReceivedTimeUtc` is after `StartTimeUtc`, this may indicate that your connections are under high load.
 
 ## Walking through a sample maintenance event
 

diff --git a/docs/Testing.md b/docs/Testing.md
@@ -16,7 +16,7 @@ This can be done either by installing Docker and running `docker compose up` in
 
 Tests default to `127.0.0.1` as their server, however you can override any of the test IPs/hostnames and ports by placing a `TestConfig.json` in the `StackExchange.Redis.Tests\` folder. This file is intentionally in `.gitignore` already, as it's for *your* personal overrides. This is useful for testing local or remote servers, different versions, various ports, etc.
 
-You can find all the JSON properties at [TestConfig.cs](https://github.com/StackExchange/StackExchange.Redis/blob/main/tests/StackExchange.Redis.Tests/Helpers/TestConfig.cs). An example override (everything not specified being a default) would look like this:
+You can find all the JSON properties at [TestConfig.cs](https://github.com/seredis/StackExchange.Redis/blob/main/tests/StackExchange.Redis.Tests/Helpers/TestConfig.cs). An example override (everything not specified being a default) would look like this:
 ```json
 {
   "RunLongRunning": true,

diff --git a/docs/index.md b/docs/index.md
@@ -62,4 +62,4 @@ Questions and Contributions
 If you think you have found a bug or have a feature request, please [report an issue][2], or if appropriate: submit a pull request. If you have a question, feel free to [contact me](https://github.com/mgravell).
 
   [1]: https://docs.microsoft.com/en-us/dotnet/standard/parallel-programming/task-parallel-library-tpl
-  [2]: https://github.com/StackExchange/StackExchange.Redis/issues?state=open
+  [2]: https://github.com/seredis/StackExchange.Redis/issues?state=open
diff --git a/src/StackExchange.Redis/ConfigurationOptions.cs b/src/StackExchange.Redis/ConfigurationOptions.cs
@@ -1209,7 +1209,7 @@ internal bool TryResp3()
             // }
             // else
             // ^^^ left for context; originally our intention was to auto-enable RESP3 by default *if* the server version
-            // is >= 6; however, it turns out (see extensive conversation here https://github.com/StackExchange/StackExchange.Redis/pull/2396)
+            // is >= 6; however, it turns out (see extensive conversation here https://github.com/seredis/StackExchange.Redis/pull/2396)
             // that tangential undocumented API breaks were made at the same time; this means that even if we fix every
             // edge case in the library itself, the break is still visible to external callers via Execute[Async]; with an
             // abundance of caution, we are therefore making RESP3 explicit opt-in only for now; we may revisit this in a major

diff --git a/src/StackExchange.Redis/ConnectionMultiplexer.cs b/src/StackExchange.Redis/ConnectionMultiplexer.cs
@@ -1474,7 +1474,7 @@ internal async Task<bool> ReconfigureAsync(bool first, bool reconfigureAll, ILog
                     ValueStopwatch? watch = null;
 
                     int iterCount = first ? 2 : 1;
-                    // This is fix for https://github.com/StackExchange/StackExchange.Redis/issues/300
+                    // This is fix for https://github.com/seredis/StackExchange.Redis/issues/300
                     // auto discoverability of cluster nodes is made synchronous.
                     // We try to connect to endpoints specified inside the user provided configuration
                     // and when we encounter an endpoint to which we are able to successfully connect,

diff --git a/src/StackExchange.Redis/FrameworkShims.cs b/src/StackExchange.Redis/FrameworkShims.cs
@@ -1,7 +1,7 @@
 #pragma warning disable SA1403 // single namespace
 
 #if NET
-// context: https://github.com/StackExchange/StackExchange.Redis/issues/2619
+// context: https://github.com/seredis/StackExchange.Redis/issues/2619
 [assembly: System.Runtime.CompilerServices.TypeForwardedTo(typeof(System.Runtime.CompilerServices.IsExternalInit))]
 #else
 // To support { get; init; } properties

diff --git a/src/StackExchange.Redis/PhysicalConnection.cs b/src/StackExchange.Redis/PhysicalConnection.cs
@@ -1855,7 +1855,7 @@ private void MatchResult(in RawResult result)
                                 _readStatus = ReadStatus.InvokePubSub;
                                 muxer.OnMessage(subscriptionChannel, subscriptionChannel, payload);
                             }
-                            // could be multi-message: https://github.com/StackExchange/StackExchange.Redis/issues/2507
+                            // could be multi-message: https://github.com/seredis/StackExchange.Redis/issues/2507
                             else if (TryGetMultiPubSubPayload(items[2], out var payloads))
                             {
                                 _readStatus = ReadStatus.InvokePubSub;

diff --git a/src/StackExchange.Redis/README.md b/src/StackExchange.Redis/README.md
@@ -3,4 +3,4 @@ StackExchange.Redis is a high-performance RESP (Redis, etc) client for .NET, ava
 - Release notes: [https://stackexchange.github.io/StackExchange.Redis/ReleaseNotes](https://stackexchange.github.io/StackExchange.Redis/ReleaseNotes)
 - NuGet package: [https://www.nuget.org/packages/StackExchange.Redis/](https://www.nuget.org/packages/StackExchange.Redis/)
 - General docs: [https://stackexchange.github.io/StackExchange.Redis/](https://stackexchange.github.io/StackExchange.Redis/)
-- Code: [https://github.com/StackExchange/StackExchange.Redis/](https://github.com/StackExchange/StackExchange.Redis/)
+- Code: [https://github.com/seredis/StackExchange.Redis/](https://github.com/seredis/StackExchange.Redis/)
diff --git a/src/StackExchange.Redis/ResultProcessor.cs b/src/StackExchange.Redis/ResultProcessor.cs
@@ -1137,7 +1137,7 @@ protected override bool SetResultCore(PhysicalConnection connection, Message mes
                         var bridge = connection.BridgeCouldBeNull;
                         var config = Parse(connection, nodes);
 
-                        // re multi-db: https://github.com/StackExchange/StackExchange.Redis/issues/2642
+                        // re multi-db: https://github.com/seredis/StackExchange.Redis/issues/2642
                         if (bridge != null && !connection.MultiDatabasesOverride)
                         {
                             bridge.ServerEndPoint.ServerType = ServerType.Cluster;

diff --git a/src/StackExchange.Redis/SocketManager.cs b/src/StackExchange.Redis/SocketManager.cs
@@ -246,7 +246,7 @@ internal static bool TryEnableTcpKeepAlive(Socket socket, EndPoint endPoint)
             {
 #if !NET10_0_OR_GREATER
                 // Prior to .NET 10, enabling TCP keep-alive on host-based endpoints fails outside of Windows.
-                // see https://github.com/StackExchange/StackExchange.Redis/issues/3086
+                // see https://github.com/seredis/StackExchange.Redis/issues/3086
                 case DnsEndPoint when !RuntimeInformation.IsOSPlatform(OSPlatform.Windows): return false;
 #endif
                 case DnsEndPoint:

diff --git a/tests/StackExchange.Redis.Tests/ClusterHandshakeNodesUnitTests.cs b/tests/StackExchange.Redis.Tests/ClusterHandshakeNodesUnitTests.cs
@@ -4,7 +4,7 @@
 
 namespace StackExchange.Redis.Tests;
 
-// context: https://github.com/StackExchange/StackExchange.Redis/pull/3043
+// context: https://github.com/seredis/StackExchange.Redis/pull/3043
 public class ClusterHandshakeNodesUnitTests(ITestOutputHelper log)
 {
     [Fact]

diff --git a/tests/StackExchange.Redis.Tests/ScanTests.cs b/tests/StackExchange.Redis.Tests/ScanTests.cs
@@ -388,7 +388,7 @@ public async Task HashScanNoValuesLarge(int pageSize)
     }
 
     /// <summary>
-    /// See <see href="https://github.com/StackExchange/StackExchange.Redis/issues/729"/>.
+    /// See <see href="https://github.com/seredis/StackExchange.Redis/issues/729"/>.
     /// </summary>
     [Fact]
     public async Task HashScanThresholds()

diff --git a/tests/StackExchange.Redis.Tests/ValkeyUnitTests.cs b/tests/StackExchange.Redis.Tests/ValkeyUnitTests.cs
@@ -21,7 +21,7 @@ public async Task IdentifyValkeyCluster(ServerType type)
 
     private sealed class InProcessValkeyLikeServer(ITestOutputHelper log) : InProcessTestServer(log)
     {
-        // see https://github.com/StackExchange/StackExchange.Redis/pull/3050
+        // see https://github.com/seredis/StackExchange.Redis/pull/3050
         protected override string ServerModeKey => "server_mode";
 
         protected override void Info(StringBuilder sb, string section)
-Original file line number
+Diff line change
@@ Expand Up @@
         }
     };
     ```
-    You can see the schema for the `AzureMaintenanceEvent` class [here](https://github.com/StackExchange/StackExchange.Redis/blob/main/src/StackExchange.Redis/Maintenance/AzureMaintenanceEvent.cs). Note that the library automatically sets the `ReceivedTimeUtc` timestamp when the event is received, so if you see in your logs that `ReceivedTimeUtc` is after `StartTimeUtc`, this may indicate that your connections are under high load.
+    You can see the schema for the `AzureMaintenanceEvent` class [here](https://github.com/seredis/StackExchange.Redis/blob/main/src/StackExchange.Redis/Maintenance/AzureMaintenanceEvent.cs). Note that the library automatically sets the `ReceivedTimeUtc` timestamp when the event is received, so if you see in your logs that `ReceivedTimeUtc` is after `StartTimeUtc`, this may indicate that your connections are under high load.
     ## Walking through a sample maintenance event
@@ Expand Down @@