Use FQBN for sketch compilation workflow job names #44
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 "Compile Examples" workflow used to do a "smoke test" sketch compilation CI check uses a job matrix to compile the sketches for all boards of interest. By default, the matrix job is named by the matrix element for that job. This element includes board data used to make board-specific job customizations. That attribute data makes the job name, which is used to identify it in the checks status UI and workflow logs, fairly cryptic. The only information of interest to a human identifying the job is the FQBN. Defining a custom job name overrides the default job naming behavior.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 "Compile Examples" workflow used to do a "smoke test" sketch compilation CI check uses a job matrix to compile the
sketches for all boards of interest.
By default, the matrix job is named by the matrix element for that job. This element includes board data used to make
board-specific job customizations. That attribute data makes the job name, which is used to identify it in the checks
status UI and workflow logs, fairly cryptic. The only information of interest to a human identifying the job is the FQBN.
Defining a custom job name overrides the default job naming behavior.