From 1a35eea731feb147a49b2a25960fca731b84439f Mon Sep 17 00:00:00 2001 From: Erik Schierboom Date: Fri, 16 Aug 2024 12:50:25 +0200 Subject: [PATCH] Fix URL for track tooling repo overview (#564) --- building/tooling/analyzers/README.md | 4 ++-- building/tooling/representers/README.md | 4 ++-- building/tooling/test-runners/README.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/building/tooling/analyzers/README.md b/building/tooling/analyzers/README.md index c12fa575..f070bfc0 100644 --- a/building/tooling/analyzers/README.md +++ b/building/tooling/analyzers/README.md @@ -7,8 +7,8 @@ Exercism's analyzers automatically assess student's submissions and provide ment Each language has its own Analyzer, written in that language. The website acts as the orchestrator between the Analyzers and students' submissions. -Each Analyzer lives in the Exercism GitHub organization in a repository named `$LANG-analyzer` (e.g. `ruby-analyzer`). -You can explore the different Analyzers [here](https://github.com/exercism?q=-analyzer). +Each Analyzer lives in the Exercism GitHub organization in a repository named `-analyzer` (e.g. [`exercism/ruby-analyzer`](https://github.com/exercism/ruby-analyzer)). +You can check out the existing Analyzers [here](https://github.com/search?q=topic%3Aexercism-analyzer&type=repositories). If you would like to get involved in helping with an existing Analyzer, please open an issue in its repository asking if there is somewhere you can help. If you would like to create an Analyzer for a language that currently does not have one, please follow the [creating a Analyzer](/docs/building/tooling/analyzers/creating-from-scratch) instructions. diff --git a/building/tooling/representers/README.md b/building/tooling/representers/README.md index fe9b77db..a2f78f1b 100644 --- a/building/tooling/representers/README.md +++ b/building/tooling/representers/README.md @@ -23,8 +23,8 @@ A notification will be sent for old solutions with a matching representation. Each language has its own representer, written in that language. The website acts as the orchestrator between the representer and students' submissions. -Each representer lives in the Exercism GitHub organization in a repository named `$LANG-representer` (e.g. `ruby-representer`). -You can explore the different representers [here](https://github.com/exercism?q=-representer). +Each representer lives in the Exercism GitHub organization in a repository named `-representer` (e.g. [`exercism/ruby-representer`](https://github.com/exercism/ruby-representer)). +You can check out the existing representers [here](https://github.com/search?q=topic%3Aexercism-representer&type=repositories). If you would like to get involved in helping with an existing Representer, please open an issue in its repository asking if there is somewhere you can help. If you would like to create a Representer for a language that currently does not have one, please follow the [creating a Representer](/docs/building/tooling/representers/creating-from-scratch) instructions. diff --git a/building/tooling/test-runners/README.md b/building/tooling/test-runners/README.md index 2642d219..2fb9bb17 100644 --- a/building/tooling/test-runners/README.md +++ b/building/tooling/test-runners/README.md @@ -12,8 +12,8 @@ Test Runners give us two advantages: Each language has its own Test Runner, written in that language. The website acts as the orchestrator between the Test Runners and students' submissions. -Each Test Runner lives in the Exercism GitHub organization in a repository named `$LANG-test-runner` (e.g. [`exercism/ruby-test-runner`](https://github.com/exercism/ruby-test-runner)). -You can explore the different Test Runners [here](https://github.com/exercism?q=-test-runner). +Each Test Runner lives in the Exercism GitHub organization in a repository named `-test-runner` (e.g. [`exercism/ruby-test-runner`](https://github.com/exercism/ruby-test-runner)). +You can check out the existing Test Runners [here](https://github.com/search?q=topic%3Aexercism-test-runner&type=repositories). If you would like to get involved in helping with an existing Test Runner, please open an issue in its repository asking if there is somewhere you can help. If you would like to create a Test Runner for a language that currently does not have one, please follow the [creating a Test Runner](/docs/building/tooling/test-runners/creating-from-scratch) instructions.