Explicitly define names for build jobs in Go release workflows #661
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The release workflows for Go-based projects use a matrix job to perform the build for each target host architecture. The matrix data is defined by a mapping. When a job name is not explicitly defined in the workflow GitHub Actions automatically generates the job name from the job ID and the matrix data. In cases where there is no matrix, or when the matrix data is a simple sequence of strings, that job name is often adequate. However, when the matrix data is more complex, the automatically generated name becomes overly verbose and cryptic (e.g., "create-nightly-artifacts (macOS_ARM64, macOS_ARM64, ubuntu-24.04-arm)"), harming the readability of the logs. In this case, an explicit human-friendly job name should be defined in the workflow.
per1234
added
type: enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The release workflows for Go-based projects use a matrix job to perform the build for each target host architecture. The matrix data is defined by a mapping.
When a job name is not explicitly defined in the workflow GitHub Actions automatically generates the job name from the job ID and the matrix data. In cases where there is no matrix, or when the matrix data is a simple sequence of strings, that job name is often adequate. However, when the matrix data is more complex, the automatically generated name becomes overly verbose and cryptic (e.g., "create-nightly-artifacts (macOS_ARM64, macOS_ARM64, ubuntu-24.04-arm)"), harming the readability of the logs. In this case, an explicit human-friendly job name should be defined in the workflow.