Skip to content

O2 linter: Be more specific about the action log section #356

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
dsekihat merged 1 commit into from
Jun 4, 2026
+2 −2
Merged

O2 linter: Be more specific about the action log section #356

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/tools/o2linter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,13 +51,13 @@ In your fork O2Physics repository go to: "Settings -> Actions -> General -> Acti
When you push to your remote branch, O2 linter will lint the files modified compared to the remote master branch in your fork.
(If you want to lint only your commits, make sure your remote master branch is up to date.)

The output can be found in the log of the GitHub action.
The output can be found in the "Run tests" step of the log of the GitHub action.

### In GitHub pull requests

O2 linter runs automatically on pull requests and lints files modified by the PR (compared to the target branch).

The total numbers of errors, warnings, and disabled issues are reported for convenience as an auto-updating comment in the PR, while the detailed breakdown per test remains available in the log of the GitHub action.
The total numbers of errors, warnings, and disabled issues are reported for convenience as an auto-updating comment in the PR, while the detailed breakdown per test remains available in the "Run tests" step of the log of the GitHub action.

The first ten errors also appear as annotations directly in the source code.

Expand Down
Loading