Skip to content

Fix typos in test runner documentation #577

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.

Sign up for GitHub

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
frostebite merged 1 commit into from
Aug 13, 2026
+2 −2
Merged

Fix typos in test runner documentation #577

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions docs/03-github/03-test-runner.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ the [`packageMode`](#packagemode) configuration option to `true`.

When testing a Unity package that has dependencies inside a scoped registry, you can set the
[`scopedRegistryUrl`](#scopedRegistryUrl) and [`registryScopes`](#registryScopes) to ensure those
depedencies can be resolved.
dependencies can be resolved.

```yaml
- uses: game-ci/unity-test-runner@v4
Expand All @@ -128,7 +128,7 @@ depedencies can be resolved.
#### Authentication with a private scoped registry

If your package has dependencies that are hosted in a private UPM registry, then testing it is
similar to tesing a project. Setup the [`scopedRegistryUrl`](#scopedRegistryUrl) and
similar to testing a project. Setup the [`scopedRegistryUrl`](#scopedRegistryUrl) and
[`registryScopes`](#registryScopes) as usual, but also include a `UPM_REGISTRY_TOKEN` when defining
your Unity License.

Expand Down
Loading