You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you have several tasks in a yaml file, the names in CI are based on the yaml file and then the platform.
It would be more useful if the labels were the task identifiers. Then the user can provide a single descriptive identifier which says what they want. If they feel they need a graphic, they can do that in the name.
Here is an example of how the current situation fails.
I don't need to see the word "tests".
OpenJDK is irrelevant except for bazel itself
for my use, the important thing is bazel version
Suggestion:
Overall option to say default the CI visible name to the task identifier.
The text was updated successfully, but these errors were encountered:
When you have several tasks in a yaml file, the names in CI are based on the yaml file and then the platform.
It would be more useful if the labels were the task identifiers. Then the user can provide a single descriptive identifier which says what they want. If they feel they need a graphic, they can do that in the name.
Here is an example of how the current situation fails.
Suggestion:
Overall option to say default the CI visible name to the task identifier.
The text was updated successfully, but these errors were encountered: