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

Trying a shorter job name for better display in GHA #761

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

mzuehlke
Copy link
Collaborator

@mzuehlke mzuehlke commented Oct 14, 2024

Before
Bildschirmfoto 2024-10-14 um 16 05 46

After:
Bildschirmfoto 2024-10-14 um 16 06 02

Feedback welcome.
I really dislike this part of the GH UI

@mzuehlke mzuehlke marked this pull request as ready for review October 15, 2024 06:18
@armanbilge
Copy link
Member

I don't have a strong preference ... this is just something we've inherited from sbt-github-actions. My thought is CI refers to the entire workflow (build, test, docs, publish, etc) vs build-and-test is a specific job that is part of CI.

I really dislike this part of the GH UI

Yep, I have struggled many times to figure out which cell of the matrix a failure happened in ...

@valencik
Copy link
Member

This is definitely an improvement in my opinion.
We get to see the Scala version and most of the JVM name.

If we could ditch the -latest suffix from the OS names, that would probably let you see everything of importance.

@mzuehlke
Copy link
Collaborator Author

With the switch from ubuntu-latest to ubuntu-22.04 I am bit reluctant to remove OS version.
"CI" was just my first idea, mostly because it is short 😉
"Test" would be another suggestion (instead of "Build and Test"

@mzuehlke
Copy link
Collaborator Author

Instead of leaving the generation of the job.name to the automation we could generate a name, but only list axes from the matrix that have more than one dimension. In this project that would remove the scala version 8always "2.12" and the project (always "sbt-typelevelJVM").

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants