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.

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

Jump to bottom

Test result key should be implemented as enum, not a string #3253

Merged
merged 3 commits into from
Oct 4, 2024
Merged

Test result key should be implemented as enum, not a string #3253

merged 3 commits into from
Oct 4, 2024
+41 −9

Commits on Oct 3, 2024

  1. Test result key should be implemented as enum, not a string 

    This is a leftover from transitioning to enums in the past.
    @happz
    happz committed Oct 3, 2024
    Configuration menu
    Copy the full SHA
    7d81513 View commit details
    Browse the repository at this point in the history

  2. squash: fix show

    @happz
    happz committed Oct 3, 2024
    Configuration menu
    Copy the full SHA
    499635c View commit details
    Browse the repository at this point in the history

  3. squash: fix test

    @happz
    happz committed Oct 3, 2024
    Configuration menu
    Copy the full SHA
    c32b7e7 View commit details
    Browse the repository at this point in the history