Skip to content
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

minor typos #5

Merged
merged 1 commit into from
Nov 18, 2023
Merged

minor typos #5

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
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ The required scopes are `api, write_repository` and the role should be Maintaine

```json
{
"provider": "gitea",
"provider": "gitlab",
"api_url": "https://<your-instance-url>/api/v4",
"project_id":"<username>/<repo_name>",
"token": "<token>"
Expand All @@ -99,7 +99,7 @@ Templaters are change operations that operate on a specific type of file, unlike

#### JSON

The JSON templater replaces values within a JSON file. Keys are provided as strings using `/` for separation, you can specify array indexes for array (e.g. `nested/field/10/tag` becomes `nested.field[10].tag`).
The JSON templater replaces values within a JSON file. Keys are provided as strings using `/` for separation, you can specify array indexes for arrays (e.g. `nested/field/10/tag` becomes `nested.field[10].tag`).

Your changeset should look like this:

Expand All @@ -120,7 +120,7 @@ The fields **MUST** exist in the file or the change will fail.

#### YAML

The YAML templater replaces values within a YAML file. Keys are provided as strings using `.` for separation, you can specify array indexes for array (e.g. `nested.field.10.tag` becomes `nested.field[10].tag`).
The YAML templater replaces values within a YAML file. Keys are provided as strings using `.` for separation, you can specify array indexes for arrays (e.g. `nested.field.10.tag` becomes `nested.field[10].tag`).

Your changeset should look like this:

Expand Down
Loading