Skip to content

feat: trigger release from minimal docs-only change #162

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
jramatowski-splunk merged 1 commit into from
Apr 24, 2026
Merged

feat: trigger release from minimal docs-only change #162

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 README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ Path to generated file with markdown for expected appinspect failures
`pass|fail`

### Manual checks review
To see checks to be verified, inspect the `result_file` from `appinspect-cli-action`. Verify manual checks and mark them as reviewed by adding them one by one into `.appinspect.manualcheck.yaml`, ex:
To see checks to be verified, inspect the `result_file` from `appinspect-cli-action`. Verify manual checks and mark them as reviewed by adding them one by one into `.appinspect.manualcheck.yaml`, for example:
```yml
name_of_manual_check_1:
comment: 'your comment'
Expand All @@ -70,7 +70,7 @@ name_of_manual_check_2:
Please note that names of validated manual checks should be aligned with those from `result_file` and your comment can't be empty.

### Failure checks review
To mark Failures as expected, add them into `.appinspect.expect.yaml` with proper comment containing ticket id of ADDON/APPCERT project associated with the exception, ex:
To mark Failures as expected, add them into `.appinspect.expect.yaml` with proper comment containing ticket id of ADDON/APPCERT project associated with the exception, for example:
```yml
name_of_exception_1:
comment: 'ADDON-123: your comment'
Expand Down
Loading