required status checks: not possible to select two jobs with same name in different workflows

[rursprung]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

Workflow Configuration

Discussion Details

let's presume i have two workflow files in a repository, .github/workflows/a.yaml and .github/workflows/b.yaml.

their exact content is irrelevant, but both of them have a build-results job (which look like this example) to collect the results from other jobs (and build matrix) together into a single job to be referenced in the required status checks.

with a single workflow file this works fine and i can just enter "build-results", find it and select it in the "Status checks that are required" on the edit rulesets UI.
however, if i have a second workflow file i cannot add that workflow anymore (in my case i've already added the first one before pushing the second file at a later state - i'm not sure what the behaviour would be if both files were new, maybe i couldn't select either?).

IMHO it should be able to differentiate between the two and e.g. show them as "a / build-results" and "b / build-results".

this also ties in with #143572: i don't even know what's going wrong since i don't actually see a list of jobs which i could select from - i have to type and hope that this is the name by which it'll find it.

[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. ⭐