Skip to content

Harden fixer paths, modifications, disabling, and commits #524

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

Open
coderabbitai wants to merge 1 commit into
base: fix/empty-linter-pattern-never-matched
Choose a base branch
from
Open

Harden fixer paths, modifications, disabling, and commits #524

Show file tree
Hide file tree
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: 4 additions & 0 deletions robot-repo-automaton/README.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -316,6 +316,10 @@ The error catalog uses S-expression format (Guile Scheme compatible):
| Apply a line-level transformation. Requires a `modification` field with spec
such as `replace-line:N:content`, `insert-before:N:content`,
`replace-pattern:regex:replacement`, `prepend:content`, or `append:content`.
For `replace-pattern`, the first unescaped colon separates the regex and
replacement. Write a colon within either field as `\:` (for example,
`replace-pattern:https?\://old:https\://new`). Regex replacement expansion is
preserved, so capture references such as `$1` and `$name` are supported.

| `create`
| Create the target file from a template or `fallback` content. Supports
Expand Down
Loading
Loading