Skip to content
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.

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

util: Coverage Report additions #563

Merged
merged 11 commits into from
Jan 12, 2025
Merged

Conversation

valarnin
Copy link
Collaborator

  • Add "other" content to coverage report
  • Add spacer row between expansions/other triggers
  • Have coverage report use zone label where appropriate
  • Clean up duplicate kPrefixToCategory
  • Add Comments column and associated field to TriggerSet
  • Add Status column

Status isn't really a good name for the column but it's 4:30am and I'm out of brainpower to think about things like names.

Hovering over the Status column's values will show the date/time of the commit (for unreleased) or tag (for released).

Example comment in screenshot was not actually committed.

image

@github-actions github-actions bot added config ui/config, ui/[module]/config util /util needs-review Awaiting review labels Jan 12, 2025
@Akurosia
Copy link
Collaborator

Would "Release Version" a better name instead of Status?
Also for tags, would there be a benefit of maybe adding a link to the github page?

@valarnin
Copy link
Collaborator Author

Renamed column, added colors, added PR info for open PRs. Maybe it makes more sense to list the open PRs first and the date second?

From an information standpoint I don't think there's any more I can do here.

Linking to a give PR/release/etc doesn't really work very well with the current table's structure, I think we'd need to rewrite the entire presentation layer to have that make sense. (css grid is making this frustrating to deal with)

image

@github-actions github-actions bot removed the needs-review Awaiting review label Jan 12, 2025
@JLGarber
Copy link
Collaborator

Probably worth reversing open PRs and the date, yes, but not a big deal either way. I think making it clear what is and isn't released yet is the big win here.

@valarnin valarnin merged commit a1008d5 into OverlayPlugin:main Jan 12, 2025
14 checks passed
github-actions bot pushed a commit that referenced this pull request Jan 12, 2025
- Add "other" content to coverage report
- Add spacer row between expansions/other triggers
- Have coverage report use zone label where appropriate
- Clean up duplicate `kPrefixToCategory`
- Add `Comments` column and associated field to `TriggerSet`
- Add `Status` column
- Add colors
- Add PRs a1008d5
github-actions bot pushed a commit to ShadyWhite/cactbot that referenced this pull request Jan 13, 2025
- Add "other" content to coverage report
- Add spacer row between expansions/other triggers
- Have coverage report use zone label where appropriate
- Clean up duplicate `kPrefixToCategory`
- Add `Comments` column and associated field to `TriggerSet`
- Add `Status` column
- Add colors
- Add PRs a1008d5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
config ui/config, ui/[module]/config util /util
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants