Problem Statement:

No-op jobs and other non-build job types (like approval and release jobs) prepend the workflow name to the GitHub status check name (e.g., workflow_name/job_name), while regular build jobs display without the workflow prefix (e.g., job_name).

This inconsistency creates challenges when:

Migrating existing jobs to no-op jobs, as GitHub required status checks must be updated

Managing branch protection rules across different job types

Maintaining consistent naming conventions across workflows

Requested Enhancement:

Provide an option to control the naming convention for no-op jobs in GitHub status checks, allowing users to choose between:

Current behavior: workflow_name/job_name

Consistent behavior: job_name (matching regular build jobs)