Improve severity labels in Actions logs and tweak colors#36993
Merged
wxiaoguang merged 10 commits intogo-gitea:mainfrom Mar 26, 2026
Merged
Improve severity labels in Actions logs and tweak colors#36993wxiaoguang merged 10 commits intogo-gitea:mainfrom
wxiaoguang merged 10 commits intogo-gitea:mainfrom
Conversation
Add support for error, warning, notice, and debug log commands with bold label prefixes and colored backgrounds matching GitHub's style. Parse both ##[cmd] and ::cmd args:: formats. Update error/warning theme colors to match GitHub's hue. Co-Authored-By: Claude (claude-opus-4-6) <noreply@anthropic.com>
GiteaBot
added
the
lgtm/need 2
silverwind
added
type/enhancement
Co-Authored-By: Claude (claude-opus-4-6) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds richer parsing and rendering of GitHub Actions “severity” log commands so Actions job logs can display consistent labeled lines (and styling hooks) for error/warning/notice/debug.
Changes:
- Extend Actions log command parsing to recognize
##[severity]and raw::severity ...::formats for warning/notice/debug (in addition to error). - Render severity lines with a bold label prefix (
Error:,Warning:, etc.) and add per-line CSS classes for styling. - Tweak theme error/warning palette variables and update frontend unit tests for the new HTML structure.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| web_src/js/components/ActionRunView.ts | Adds parsing for ::severity ...:: commands and injects severity label spans into rendered log messages. |
| web_src/js/components/ActionRunView.test.ts | Updates expected HTML output and adds coverage for new severity parsing/rendering cases (partial). |
| web_src/js/components/ActionRunJobView.vue | Adds per-line class names for severity and introduces new CSS rules for label styling and some severity visuals. |
| web_src/css/themes/theme-gitea-light.css | Adjusts global --color-error-* and --color-warning-* theme variables. |
| web_src/css/themes/theme-gitea-dark.css | Adjusts global --color-error-* and --color-warning-* theme variables. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-Authored-By: Claude (claude-opus-4-6) <noreply@anthropic.com>
Error, success, and info backgrounds and borders were too faint compared to warning. Make them similarly visible. Co-Authored-By: Claude (claude-opus-4-6) <noreply@anthropic.com>
Co-Authored-By: Claude (claude-opus-4-6) <noreply@anthropic.com>
Use filter: saturate(2) for message headers instead of separate color overrides. Match perceived lightness across all severity text colors. Use Tailwind classes in devtest page. Increase saturation of light theme severity backgrounds and borders. Co-Authored-By: Claude (claude-opus-4-6) <noreply@anthropic.com>
silverwind
changed the title
Co-Authored-By: Claude (claude-opus-4-6) <noreply@anthropic.com>
wxiaoguang
approved these changes
Mar 26, 2026
GiteaBot
added
lgtm/need 1
…ateElement` Move the saturate(2) filter from base.css to message.css to cover all message types and remove the now-obsolete partial rule. Add color: inherit for consistency. Use document.createElement instead of createElementFromAttrs with null attrs. Co-Authored-By: Claude (claude-opus-4-6) <noreply@anthropic.com>
Co-Authored-By: Claude (claude-opus-4-6) <noreply@anthropic.com>
bircni
approved these changes
Mar 26, 2026
GiteaBot
added
lgtm/done
Contributor
|
You can see that if our framework is designed correctly (I made the changes to |
Member
Author
|
Yes, it's clean-ish. Still I run Claude with max effort and always |
Contributor
|
The color looks dirty (more grey) than before 
|
Member
Author
|
Looks completely fine to me on that screenshot. Which color are you referring to? The only wrong think i spot there is the double top border. |
Contributor
|
The blue color looks dirty. Before 
After 
|
Member
Author
|
On my screen the hue of text and background seems to match, is that what you mean? The background is more intense, but I think that's fine. If you want, I can make exact color copies from Primer (https://primer.style/product/components/banner/guidelines/#variant). |
Contributor
|
The colors defined in https://primer.style/product/components/banner/guidelines/#variant are indeed much better and clearer |
Member
Author
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.
Add support for error, warning, notice, and debug log commands with bold label prefixes and colored backgrounds matching GitHub's style. Parse both
##[cmd]and::cmd args::formats.Also improved the severity colors globally and added a devtest page for these.