We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The way to use the orb as a job is to specify - shellcheck/check:
- shellcheck/check:
As a result, in github we get this output:
The name check isn't very descriptive in a project with a lot of other checks.
check
Of course we can workaround by making our own job, but this is more work than what could be needed.
Thanks!
The text was updated successfully, but these errors were encountered:
@julienw Thanks for the heads up! For any orb job, you can pass along a name parameter to a job to override the name, like so:
name
version: 2.1 orbs: shellcheck: circleci/shellcheck@volatile workflows: test: jobs: - shellcheck/check: name: "Shellcheck"
Sorry, something went wrong.
No branches or pull requests
Describe Request:
The way to use the orb as a job is to specify
- shellcheck/check:
As a result, in github we get this output:
The name
check
isn't very descriptive in a project with a lot of other checks.Of course we can workaround by making our own job, but this is more work than what could be needed.
Thanks!
The text was updated successfully, but these errors were encountered: