commit 7085acd6b0bab0de93441b0281f0de8056860f58
author Alex Hong <hongalex@google.com> Mon Dec 23 15:49:17 2024 -0800
committer Gopher Robot <gobot@golang.org> Wed Dec 25 15:46:11 2024 -0800
tree 919628d8e9834f5a3b7a597a264d37287e8be50e
parent a5897f469d06a668abd680af4a11e2f981ef0749

all: fix broken image links

Some links were broken due to a contributor's name change.

Change-Id: Ibb766de3aa9c9f89cca81d3d6e26dddc4d7893cf
Reviewed-on: https://go-review.googlesource.com/c/wiki/+/638298
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Commit-Queue: Ian Lance Taylor <iant@golang.org>
Auto-Submit: Ian Lance Taylor <iant@golang.org>

Modules.md

diff --git a/Modules.md b/Modules.md
index 187efa4..4691308 100644
--- a/Modules.md
+++ b/Modules.md
@@ -1129,7 +1129,7 @@
     |-- go.mod
     `-- vub
 ```
-![Fig. A top-level module's path is a prefix of another module's path.](https://github.com/jadekler/module-testing/blob/master/imagery/multi_module_repo.png)
+![Fig. A top-level module's path is a prefix of another module's path.](https://github.com/jeanbza/module-testing/blob/master/imagery/multi_module_repo.png)
 
 _Fig. A top-level module's path is a prefix of another module's path._
 

Projects.md

diff --git a/Projects.md b/Projects.md
index d6ded60..fd02faa 100644
--- a/Projects.md
+++ b/Projects.md
@@ -1797,7 +1797,7 @@
   * [SuperSaaS API Client](https://github.com/SuperSaaS/supersaas-go-api-client) - HTTP client library for the supersaas.com scheduling/bookings/appointments API
   * [Tideland golib](https://github.com/tideland/golib) - Web package for REST request handling
   * [Vantaa](https://github.com/nathandao/vantaa) - A modular blogging API engine written in Go, Neo4j and Polymer.
-  * [websiteskeleton](https://github.com/jadekler/git-go-websiteskeleton) - Simple net/http website skeleton
+  * [websiteskeleton](https://github.com/jeanbza/git-go-websiteskeleton) - Simple net/http website skeleton
   * [webtf](http://code.google.com/p/webtf/) - Web app to graphical visualization of twitter timelines using the HTML5
   * [Wikifeat](https://github.com/rhinoman/wikifeat) - Extensible wiki system using CouchDB written in Golang
   * [jweb](https://gitlab.com/drjele-go/jweb) - A Symfony(https://symfony.com/) inspired framework, written in Go

Resolving-Problems-From-Modified-Module-Path.md

diff --git a/Resolving-Problems-From-Modified-Module-Path.md b/Resolving-Problems-From-Modified-Module-Path.md
index c88ba59..1ce49c6 100644
--- a/Resolving-Problems-From-Modified-Module-Path.md
+++ b/Resolving-Problems-From-Modified-Module-Path.md
@@ -75,7 +75,7 @@
 
 However, there is one situation that ends up being quite a bit more involved: when there are cycles in the module dependency graph. Consider this module dependency graph:
 
-![Module Dependency Graph With A Cycle](https://github.com/jadekler/module-testing/blob/master/imagery/Mod%20Graph%20With%20Cycle.jpg)
+![Module Dependency Graph With A Cycle](https://github.com/jeanbza/module-testing/blob/master/imagery/Mod%20Graph%20With%20Cycle.jpg)
 
 And, let's imagine that `some/lib` used to depend on `github.com/golang/lint`.
 
@@ -99,7 +99,7 @@
 
 Visualized with [golang.org/x/exp/cmd/modgraphviz](https://pkg.go.dev/golang.org/x/exp/cmd/modgraphviz):
 
-![A Module Dependency Graph With Trailing History](https://github.com/jadekler/module-testing/blob/master/imagery/graph1.png)
+![A Module Dependency Graph With Trailing History](https://github.com/jeanbza/module-testing/blob/master/imagery/graph1.png)
 
 Here we see that even though the last several versions of `some/lib` correctly depend on `golang.org/x/lint`, the fact that `some/lib` and `some-other/lib` share a cycle mean that there's very likely to be a path far back in time.
 
@@ -118,7 +118,7 @@
 some-other/lib@v2.5.4 some/lib@v1.7.1
 ```
 
-![A Module Dependency Graph Without Trailing History](https://github.com/jadekler/module-testing/blob/master/imagery/graph2.png)
+![A Module Dependency Graph Without Trailing History](https://github.com/jeanbza/module-testing/blob/master/imagery/graph2.png)
 
 Since `some/lib` and `some-other/lib` depend on each other at the same version, there's no path backwards in time to a point where `github.com/golang/lint` is provided.
 
@@ -161,9 +161,9 @@
 
 This example explained the process for removing historical trails when there exists a cycle involving two packages in a graph, but what about if there are cycles involving more packages? For example, consider the following graphs:
 
-![Module Dependency Graph With Four Related Cycles](https://github.com/jadekler/module-testing/blob/master/imagery/Mod%20Graph%20With%204%20Cycle_%20A.jpg)
+![Module Dependency Graph With Four Related Cycles](https://github.com/jeanbza/module-testing/blob/master/imagery/Mod%20Graph%20With%204%20Cycle_%20A.jpg)
 
-![Module Dependency Graph With One Four Vertex Cycle](https://github.com/jadekler/module-testing/blob/master/imagery/Mod%20Graph%20With%204%20Cycle_%20B.jpg)
+![Module Dependency Graph With One Four Vertex Cycle](https://github.com/jeanbza/module-testing/blob/master/imagery/Mod%20Graph%20With%204%20Cycle_%20B.jpg)
 
 Each of these graphs involve cycles (the latter example) or interconnected modules (the former example) involving four modules, instead of the simple two module example we saw earlier. The process is largely the same, though, but this time in step 3 and 5 we're going to bump all four modules to non-existent future versions of each other, and similarly in steps 4 and 6 we're going to test all four modules, and in step 7 fix the go.sum of all four modules.