Skip to content

Commit 8544c94

Browse files
Fix URL for track tooling repo overview
1 parent af14a71 commit 8544c94

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

building/tooling/analyzers/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ Exercism's analyzers automatically assess student's submissions and provide ment
77
Each language has its own Analyzer, written in that language.
88
The website acts as the orchestrator between the Analyzers and students' submissions.
99

10-
Each Analyzer lives in the Exercism GitHub organization in a repository named `$LANG-analyzer` (e.g. `ruby-analyzer`).
11-
You can explore the different Analyzers [here](https://github.com/exercism?q=-analyzer).
10+
Each Analyzer lives in the Exercism GitHub organization in a repository named `<track_slug>-analyzer` (e.g. [`exercism/ruby-analyzer`](https://github.com/exercism/ruby-analyzer)).
11+
You can check out the existing Analyzers [here](https://github.com/search?q=topic%3Aexercism-analyzer&type=repositories).
1212

1313
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.
1414
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.

building/tooling/representers/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,8 @@ A notification will be sent for old solutions with a matching representation.
2323
Each language has its own representer, written in that language.
2424
The website acts as the orchestrator between the representer and students' submissions.
2525

26-
Each representer lives in the Exercism GitHub organization in a repository named `$LANG-representer` (e.g. `ruby-representer`).
27-
You can explore the different representers [here](https://github.com/exercism?q=-representer).
26+
Each representer lives in the Exercism GitHub organization in a repository named `<track_slug>-representer` (e.g. [`exercism/ruby-representer`](https://github.com/exercism/ruby-representer)).
27+
You can check out the existing representers [here](https://github.com/search?q=topic%3Aexercism-representer&type=repositories).
2828

2929
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.
3030
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.

building/tooling/test-runners/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,8 @@ Test Runners give us two advantages:
1212
Each language has its own Test Runner, written in that language.
1313
The website acts as the orchestrator between the Test Runners and students' submissions.
1414

15-
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)).
16-
You can explore the different Test Runners [here](https://github.com/exercism?q=-test-runner).
15+
Each Test Runner lives in the Exercism GitHub organization in a repository named `<track_slug>-test-runner` (e.g. [`exercism/ruby-test-runner`](https://github.com/exercism/ruby-test-runner)).
16+
You can check out the existing Test Runners [here](https://github.com/search?q=topic%3Aexercism-test-runner&type=repositories).
1717

1818
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.
1919
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.

0 commit comments

Comments
 (0)