branch protections, job names, and matrix jobs

For protected branches in GitHub, we have to go and select each job individually. Worse, these jobs appear to be identified by the name field, which means that small tweaks to a workflow to make it _read_ better (e.g. renaming “Build ubuntu-latest g+±7 Release SHARED” to “Ubuntu Release (g++, shared)” will break branch protections… but changing the branch protection in the settings will apply before the workflow is merged from PR into the protected branch. (Otherwise you couldn’t merge the branch.)

Further, jobs with a large matrix - like a native-code project targetting multiple platforms, compilers, and build configurations - can end up with a build job with a matrix with a lot of jobs. Each of these have to be selected individually. If a new platform or configuration is added or removed, branch protections have to be updated.

It would be super awesome to be able to mark a _workflow_ as required. Further, it would be awesome for GitHub to identify the checks in branch protections by some kind of stable(ish) identifier rather than the user-friendly name of the job.

The end goal really would be able to somehow define a ci.yml workflow and tag it (and all its contained jobs) as required for branch protection purposes.

2 Likes

> It would be super awesome to be able to mark a _workflow_ as required. Further, it would be awesome for GitHub to identify the checks in branch protections by some kind of stable(ish) identifier rather than the user-friendly name of the job.

> The end goal really would be able to somehow define a ci.yml workflow and tag it (and all its contained jobs) as required for branch protection purposes.

@seanmiddleditch - Thanks for sharing your thoughts on branch protections and GitHub Actions with us. We’ve noted this internally for our product team’s consideration, though we can’t make any promises on specific changes.

If you have any additional product feedback or feature requests, we suggest writing in to our new contact form – that’s where our team is collective product feedback for GitHub Actions and other GitHub features:

https://support.github.com/contact/feedback?contact%5Bcategory%5D=actions