Overview
CircleCI status updates in GitHub pull requests or commit display job names differently depending on the job type. Approval, release, and no-op jobs include both the workflow name and job name (e.g., ci/circleci: build_and_deploy/approval-deploy), while regular jobs display only the job name (e.g., ci/circleci: build). This is the expected behavior in CircleCI's current implementation.
Solution
This naming convention difference is intentional and helps distinguish between different job types in your status update:
Regular Jobs display as:
- Format:
ci/circleci: <job_name> - Example:
ci/circleci: build - Example:
ci/circleci: rspec
Approval Jobs, Release Jobs and No-Op Jobs display as:
- Format:
ci/circleci: <workflow_name>/<job_name> - Example:
ci/circleci: build_and_deploy/approval-deploy - Example:
ci/circleci: build_and_deploy/no-op-job
This behavior is working as designed. The workflow name prefix for approval, release, and no-op jobs provides additional context since these jobs typically require manual intervention or represent conditional workflow states. Regular jobs that execute automatically do not require this additional context and display with the simpler naming format.
If you need to identify which workflow a regular job belongs to, you can click through to the CircleCI dashboard, where the full workflow context is visible.
Feature Request
While we recognize this difference as challenges for some customers, changing the build job naming pattern would be a breaking change for existing customers who depend on the current behavior. We're tracking this and gathering customer feedback. Please feel free to share your ideas about in the following link:
https://circleci.canny.io/cloud-feature-requests/p/consistent-github-status-check-naming-for-non-build-jobs-no-op-release-and-appro
Comments
Article is closed for comments.