fix: Ensure CI systems recognize linter output sections - #7650
Merged
Conversation
Changed logging levels for console linter section markers to `info`. This ensures CI/CD platforms like GitHub Actions and GitLab CI correctly interpret the section annotation commands, while visual cues (e.g.,⚠️ , ❌) continue to indicate warning or error statuses in the console output.
nvuillam
requested review from
Kurt-von-Laven,
bdovaz and
echoix
as code owners
April 26, 2026 00:48
Contributor
✅
|
nvuillam
force-pushed
the
fixes/github-output
branch
from
April 26, 2026 00:57
8dab62f to
847567a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Fix logging with latest python version