Skip to content

CLI: describe the slug placeholder #582

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 27, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion building/tooling/cli.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,11 @@ You can add support for your language by adding an entry to that [configuration

### Test command placeholders

There are two placeholders that can be used in the track-specific command:
There are three placeholders that can be used in the track-specific command:

- `{{test_files}}`: a space-separated list of the test files (as found in the `.files.test` key in the exercise's `.meta/config.json` file)
- `{{solution_files}}`: a space-separated list of the solution files (as found in the `.files.solution` key in the exercise's `.meta/config.json` file)
- `{{slug}}`: the exercise slug (as found in the exercise's `slug` key in the tracks's root `config.json` file)

Here is an [example pull request][example-pr] that adds support for the Arturo language.

Expand Down