bazelbuild / bazelbuild/continuous-integration
The task identifier should be the default name
- Dominant language
- Python
- Stars
- 302
- Forks
- 194
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 41
Description
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.
Contributor guide
Research direction
No file, test, or entry point is named. Start by locating the code that generates CI-visible names for tasks from a YAML file, then confirm how an overall naming option would affect the existing labels; done means task identifiers are used by default while still allowing a descriptive graphic name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, yaml
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100