Updated repository link.

.github/workflows/ci.yml

@@ -23,7 +23,7 @@ jobs:
         path: elk
     - uses: actions/checkout@v4
       with:
-        repository: eclipse/elk-models
+        repository: eclipse-elk/elk-models
         path: elk-models
     # Prepare and use a cache for maven
     - uses: actions/cache@v4

.github/workflows/nightly.yml

@@ -25,7 +25,7 @@ jobs:
         path: elk
     - uses: actions/checkout@v4
       with:
-        repository: eclipse/elk-models
+        repository: eclipse-elk/elk-models
         path: elk-models
     # Prepare and use a cache for maven
     - uses: actions/cache@v4

CONTRIBUTING.md

@@ -32,9 +32,9 @@ Information regarding source code management, builds, and more.
 
 The project maintains the following source code repositories
 
-* https://github.com/eclipse/elk
-* https://github.com/eclipse/elk-models
-* https://github.com/eclipse/elk-website
+* https://github.com/eclipse-elk/elk
+* https://github.com/eclipse-elk/elk-models
+* https://github.com/eclipse-elk/elk-website
 
 ## Eclipse Contributor Agreement
 

NOTICE.md

@@ -26,8 +26,8 @@ SPDX-License-Identifier: EPL-2.0
 
 The project maintains the following source code repositories:
 
-* https://github.com/eclipse/elk
-* https://github.com/eclipse/elk-models
+* https://github.com/eclipse-elk/elk
+* https://github.com/eclipse-elk/elk-models
 
 ## Third-party Content
 

README.md

@@ -1,5 +1,5 @@
 <p align="center">
-  <img src="https://raw.githubusercontent.com/eclipse/elk/master/docs/static/img/elk_with_text.svg?sanitize=true" height="150"> 
+  <img src="https://raw.githubusercontent.com/eclipse-elk/elk/master/docs/static/img/elk_with_text.svg?sanitize=true" height="150"> 
 </p>
 
 Diagrams and visual languages are a great thing,
@@ -20,7 +20,7 @@ and can thus also be used outside of Eclipse.
 
 ## Example Layout
 
-![](https://raw.githubusercontent.com/eclipse/elk/master/docs/static/img/example_layout_complexRouter.svg?sanitize=true)
+![](https://raw.githubusercontent.com/eclipse-elk/elk/master/docs/static/img/example_layout_complexRouter.svg?sanitize=true)
 
 ## Repository Structure
 
@@ -39,7 +39,7 @@ The repository's structure is pretty straightforward. We only have a few folders
 * `setups`:
   Contains our Oomph setup files.
 * `tests`:
-  Contains unit tests. Note that we have [a whole repository](https://github.com/eclipse/elk-models/) dedicated to test models.
+  Contains unit tests. Note that we have [a whole repository](https://github.com/eclipse-elk/elk-models/) dedicated to test models.
 
 
 ## Building ELK

build/Jenkinsfile

@@ -163,7 +163,7 @@ spec:
               ]
             ],
             submoduleCfg: [],
-            userRemoteConfigs: [[url: 'https://github.com/eclipse/elk.git']]
+            userRemoteConfigs: [[url: 'https://github.com/eclipse-elk/elk.git']]
           ]
         )
 
@@ -185,7 +185,7 @@ spec:
               ]
             ],
             submoduleCfg: [],
-            userRemoteConfigs: [[url: 'https://github.com/eclipse/elk-models.git']]
+            userRemoteConfigs: [[url: 'https://github.com/eclipse-elk/elk-models.git']]
           ]
         )
       }

build/RELEASE.md

@@ -66,5 +66,5 @@ This is a summary of the information on [this page](https://central.sonatype.org
 
 ## GitHub Management
 
-1. Close the release milestone [on GitHub](https://github.com/eclipse/elk/milestones).
-1. Create a new release [on GitHub](https://github.com/eclipse/elk/releases) with a release tag named `vVERSION` (for instance, `v0.4.0`).
+1. Close the release milestone [on GitHub](https://github.com/eclipse-elk/elk/milestones).
+1. Create a new release [on GitHub](https://github.com/eclipse-elk/elk/releases) with a release tag named `vVERSION` (for instance, `v0.4.0`).

build/pom.xml

@@ -447,9 +447,9 @@
 
   <!-- Information about where the ELK code lives. -->
   <scm>
-    <connection>scm:git:git://github.com/eclipse/elk.git</connection>
-    <developerConnection>scm:git:ssh://[email protected]:eclipse/elk.git</developerConnection>
-    <url>https://github.com/eclipse/elk</url>
+    <connection>scm:git:git://github.com/eclipse-elk/elk.git</connection>
+    <developerConnection>scm:git:ssh://[email protected]:eclipse-elk/elk.git</developerConnection>
+    <url>https://github.com/eclipse-elk/elk</url>
   </scm>
 
 

build/releng/publish-website.sh

@@ -18,7 +18,7 @@ then
 fi
 
 # Produce a shallow clone of the repository
-git clone --depth 1 [email protected]:eclipse/elk-website.git website
+git clone --depth 1 [email protected]:eclipse-elk/elk-website.git website
 
 # Synchronize the website over to the repository
 rsync -crv --delete --exclude=".*/" --exclude=".*" --exclude="CODE_OF_CONDUCT.md" --exclude="CONTRIBUTING.md" --exclude="LICENSE.md" --exclude="NOTICE.md" --exclude="README.md" --exclude="SECURITY.md" elk/docs/public/ website

docs/content/blog/posts/2022/22-11-17-libavoid.md

@@ -61,4 +61,4 @@ They are included in ELK's [reference documentation](/reference.html), but you c
  * [RoutingOption](https://www.adaptagrams.org/documentation/namespaceAvoid.html#abc707ccbd6a0a7c29c124162c864ca05)
  * [RoutingParameter](https://www.adaptagrams.org/documentation/namespaceAvoid.html#a8a0154ae39129e7737d98e5a83daed19)
 
-That's it for now. Please try this new integration and give us feedback on the [ELK repository](https://github.com/eclipse/elk)!
+That's it for now. Please try this new integration and give us feedback on the [ELK repository](https://github.com/eclipse-elk/elk)!

docs/content/documentation/algorithmdevelopers/unittesting.md

@@ -67,7 +67,7 @@ public ElkNode produceGraph() {
 
 ### Load Graphs From Disk
 
-Graphs stored in ELK's [models repository](https://github.com/eclipse/elk-models) can be used directly in tests. You specify graphs to be loaded through lists of `ModelResourcePath`, which accepts paths relative to the models repository:
+Graphs stored in ELK's [models repository](https://github.com/eclipse-elk/elk-models) can be used directly in tests. You specify graphs to be loaded through lists of `ModelResourcePath`, which accepts paths relative to the models repository:
 
 ```java
 @GraphResourceProvider

docs/content/documentation/contributors/buildingelk.md

@@ -33,7 +33,7 @@ A few notes:
 Due to some tycho/surefire issue the unit tests cannot be executed with Java 9 and 10.
 {{% /note %}}
 
-The unit tests require our [models repository](https://github.com/eclipse/elk-models) to be checked out as well. If it is, the following command line will run the tests (note that the command line is split in order to improve readability):
+The unit tests require our [models repository](https://github.com/eclipse-elk/elk-models) to be checked out as well. If it is, the following command line will run the tests (note that the command line is split in order to improve readability):
 
 ```bash
 mvn
@@ -64,7 +64,7 @@ mvn
 
 The documentation website is our source of documentation. The main build produces reference documentation which is part of the website from our metadata files. The documentation website itself is then built with [Hugo](https://gohugo.io/), a static website generator. The website is setup in a way to be browsable both online and offline.
 
-[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/eclipse/elk)
+[![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/eclipse-elk/elk)
 
 To actually build the documentation website, go to the repository's `docs/` folder and simply execute the following command:
 

docs/content/documentation/contributors/developmentworkflow.md

@@ -15,11 +15,11 @@ Once you [have everything set up]({{< relref "documentation/contributors/develop
 
 1. **Find a Git Repository to Work With**
 
-    While working you will probably want to create a bunch of commits and push them to a repository. However, our installer by default simply clones our official ELK repository at GitHub, which you don't have permission to write to. What you will want to do, thus, is to get your hands on another GitHub repository that you do have permission to write to. The best way is to simply fork our main repository by clicking the _Fork_ link at the upper right corner of [our repository page](https://github.com/eclipse/elk). Add your new repository as a second remote to your local clone and push your commits there.
+    While working you will probably want to create a bunch of commits and push them to a repository. However, our installer by default simply clones our official ELK repository at GitHub, which you don't have permission to write to. What you will want to do, thus, is to get your hands on another GitHub repository that you do have permission to write to. The best way is to simply fork our main repository by clicking the _Fork_ link at the upper right corner of [our repository page](https://github.com/eclipse-elk/elk). Add your new repository as a second remote to your local clone and push your commits there.
 
 1. **Tickets**
 
-    Of course we have [a list of issues](https://github.com/eclipse/elk/issues). If you want to work on one of them, you should mention your intentions there to let us know that we should not start working on the issue ourselves. Also, we might have helpful input for you to think about. If you want to implement a feature that we do not have an issue for yet, open one.
+    Of course we have [a list of issues](https://github.com/eclipse-elk/elk/issues). If you want to work on one of them, you should mention your intentions there to let us know that we should not start working on the issue ourselves. Also, we might have helpful input for you to think about. If you want to implement a feature that we do not have an issue for yet, open one.
 
 1. **Proper Commit Messages**
 
@@ -44,4 +44,4 @@ Once you [have everything set up]({{< relref "documentation/contributors/develop
 
 1. **Contributing Your Code**
 
-    To actually contribute your code to the ELK project, go [to our pull requests page](https://github.com/eclipse/elk/pulls) and click _New pull request_. Since you want us to pull in changes from your fork, click the _Compare across forks_ link and select the branch that contains the relevant changes. We will then review your code. Chances are that we will reject your pull request on your first try and ask you to make some changes. Don't let that discourage you (also, we try to be nice about it). Simply make the changes and create another pull request.
+    To actually contribute your code to the ELK project, go [to our pull requests page](https://github.com/eclipse-elk/elk/pulls) and click _New pull request_. Since you want us to pull in changes from your fork, click the _Compare across forks_ link and select the branch that contains the relevant changes. We will then review your code. Chances are that we will reject your pull request on your first try and ask you to make some changes. Don't let that discourage you (also, we try to be nice about it). Simply make the changes and create another pull request.

docs/content/documentation/contributors/developmentworkflow/installingwithoomph.md

@@ -31,6 +31,6 @@ Setting up an Eclipse to work on the _Eclipse Layout Kernel_ is comparatively ea
 
     {{< image src="oomph-install_step5.png" alt="Oomph Installation, Step 5" >}}
 
-1. Make sure everything looks good. You can usually leave the defaults, although you may need to change the _Eclipse Layout Kernel Github repository_ URL to whatever you see when you click on _Clone or download_ [on our repository page](https://github.com/eclipse/elk). Clicking _Next_ will allow you to review what the installer wants to do. Unless you understand what that is, simply ignore it and click _Finish_.
+1. Make sure everything looks good. You can usually leave the defaults, although you may need to change the _Eclipse Layout Kernel Github repository_ URL to whatever you see when you click on _Clone or download_ [on our repository page](https://github.com/eclipse-elk/elk). Clicking _Next_ will allow you to review what the installer wants to do. Unless you understand what that is, simply ignore it and click _Finish_.
 
 1. Once the setup has finished the basic installation, your new Eclipse will open and proceed to clone the GitHub repository and to set everything up properly. Once all ELK projects appear in your workspace, you're set and ready to start developing.

docs/content/documentation/tooldevelopers/graphdatastructure/elktextformat.md

@@ -8,4 +8,4 @@ menu:
 ---
 
 Documentation is coming soon. For the moment you can find an example
-on [github](https://github.com/eclipse/elk/pull/106#issuecomment-268772479).
+on [github](https://github.com/eclipse-elk/elk/pull/106#issuecomment-268772479).

docs/content/downloads/releasenotes/release-0.1.1.md

@@ -16,6 +16,6 @@ menu:
 
 A bugfix release.
 
-* Fixed a problem where edges with labels end up being routed in an ambiguous way. ([#96](https://github.com/eclipse/elk/issues/96)).
+* Fixed a problem where edges with labels end up being routed in an ambiguous way. ([#96](https://github.com/eclipse-elk/elk/issues/96)).
 
 View the release [at Eclipse](https://projects.eclipse.org/projects/modeling.elk/releases/0.1.1) for links to the list of closed issues.