[Azure Pipelines] avoid parenthesis in job names #17265
Merged
Conversation
This file contains 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 Azure Pipelines integration with GitHub Checks produces checks on the form "$pipelineName ($jobName)", leading to check names like "Azure Pipelines (tools/wptrunner/ unittests (macOS))". Use colons as separator instead, like the existing "wpt.fyi hook" jobs. Also change some step names for consistency.
|
@Hexcles @lukebjerring does anything on the wpt.fyi side depend on the job names? I suspect not, right? |
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 Azure Pipelines integration with GitHub Checks produces checks on
the form "$pipelineName ($jobName)", leading to check names like
"Azure Pipelines (tools/wptrunner/ unittests (macOS))". Use colons as
separator instead, like the existing "wpt.fyi hook" jobs.
Also change some step names for consistency.