Hard to find/know correct values for "Require status checks to pass" rule set

[farski]

Select Topic Area

Product Feedback

Body

Thanks to the recent teams plan release (🎉), I've started looking at converting some branch rules to rule sets, and adding new rules. One thing I'm looking at is the "Require status checks to pass" rule.

When defining the status checks that are required, you basically have to type in an arbitrary string to select the status check, but currently it is very hard to know what value to actually put in. When configuring this rule within a single repo, the input field does have a type-ahead suggestion feature, but I have run into cases where that sometimes gets confused and doesn't provide accurate results (or provides several different options for the same status check.

For example, I have a repo with a workflow called Check project standards (check-project-std.yml), which runs several jobs calling shared workflows (e.g., a job called check-javascript that uses: prx/.github/.github/workflows/check-project-std-javascript.yml@main) The shared workflow then also has a job that it runs (in this case, another job also called check-javascript).

The correct way to require this workflow to run is, apparently, to configure it as check-javascript / check-javascript.

Which is to say, it's not the value that appears on the pull request review page:

Or the commit status popover

Or any of these possible values:

• Check project standards / check-javascript / check-javascript (push)
• Check project standards / check-javascript / check-javascript
• check-project-std / check-javascript / check-javascript
• check-project-standards / check-javascript / check-javascript

Which you are various ways the same check appears depending on where/when you look, or what you may try to invent if the value you try doesn't work.

At the org level, the input field does not provide typeahead or any suggestions, so you are on your own in terms of figuring out what the correct value should be.

It would be great if there were somewhere on a status check that revealed the specific string that is used when required checks are being evaluated. Or at least some documentation that clearly describes how to derive that value from a given workflow. Because right now it seems like trial and error.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐