Check run names should be namespaced by application in statuses contexts #213273
Unanswered
xmo-odoo
asked this question in
Pull Requests
Replies: 1 comment
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
Body
Historically, statuses are "flat" and get namespaced in an ad-hoc manner (usually via
/) in order for multiple integrations not to overwrite one another's statuses.Check runs don't have this issue since they are segregated per application, and in the "Checks" page every application gets its little foldable area with all of its check runs:


and when opening the run, its name gets neatly namespaced by application:
However when checks are displayed in a statuses context, the

nameof the check is the only thing that appears:so now check authors have to decide whether to
Prior art:


Github's own actions get the same namespacing in status contexts as they get in the checks page:
We just need the same behavior for check runs.
All reactions