Repository navigation
Update Managing Rulesets in regards to status checks #41757
Description
Code of Conduct
- I have read and agree to the GitHub Docs project's Code of Conduct
What article on docs.github.com is affected?
What part(s) of the article would you like to see updated?
The Require Status Checks Before Merging section should more clearly mention that Github Actions (through their jobs) can be configured as status checks. The Github documentation page for status checks does mention this, however on the Managing Rulesets page it does not. More importantly, there should be instructions on how to add a workflow job as a status check on this page--I was unable to find how to do this in any official documentation available. A workflow's job-level name key can be used to add a status check in a ruleset. This should either be explained in full on the Managing Rulesets page, and if not there, then it should either be its own page or perhaps as part of the status check documentation. Providing users a brief example/step-by-step guide is not only helpful, but makes this process more transparent AND highly reputable since it would be in official documentation itself.
Additional information
Feel free to message me with any questions or feedback. Thank you!
Activity
welcome commentedon Dec 9, 2025
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
Sharra-writes commentedon Dec 16, 2025
@mcummings128 Thanks for opening an issue! I'll take this to the Actions team and see how they feel about those suggestions.
github-actions commentedon Jan 20, 2026
A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.
github-actions commentedon Mar 3, 2026
A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.
mcummings128 commentedon Mar 19, 2026
Has any progress been made on this issue? Thank you!
Sharra-writes commentedon Mar 20, 2026
@mcummings128 There has not, but I was looking for something to poke the Actions team about this morning, and here you are in my queue. I'm going to use this issue to see if they have time to talk to me.
github-actions commentedon Jul 31, 2026
Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀
github-actions commentedon Aug 31, 2026
This is a gentle reminder for the Technical Content team that this issue is waiting for technical review by a subject matter expert (SME).
github-actions commentedon Oct 5, 2026
A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.