# OT question about GitHub checks
**URL:** https://forum.syncthing.net/t/ot-question-about-github-checks/22577
**Category:** Development
**Created:** [August 9, 2024, 12:01am UTC](https://forum.syncthing.net/t/ot-question-about-github-checks/22577 "2024-08-09T00:01:41Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@acolomb](https://forum.syncthing.net/u/acolomb)
#### Post date: [August 9, 2024, 12:01am UTC](https://forum.syncthing.net/t/ot-question-about-github-checks/22577/1 "2024-08-09T00:01:41Z")
Hi maintainers,
while working on a different open source project, I face the challenge of adding a “check” to GitHub that is automatically run on each commit. But if it fails, that should not mark the whole commit / PR as failed.
In the Syncthing main repo, we already have such “not required” checks running. Could someone with access to the repository settings please show how to set up such a distinction between required and optional checks? I think it will be under the branch protection settings, but could also need some YAML adjustments? Ideally with screenshots, please 🙂
I’m not very knowledgeable with GitHub CI in general. Others have already tried to find the settings, but so far no luck.
For reference: [Type annotations in canopen · Issue #358 · christiansandberg/canopen · GitHub](https://github.com/christiansandberg/canopen/issues/358#issuecomment-2221272606)
Thank you very much in advance!
---
### Author:  [@Nummer378](https://forum.syncthing.net/u/Nummer378)
#### Post date: [August 9, 2024, 12:46am UTC](https://forum.syncthing.net/t/ot-question-about-github-checks/22577/2 "2024-08-09T00:46:08Z")
If a PR cannot be merged due to a failing check, then that’s a branch rule defined in the project.
To set a specific check as not required, go to Settings → Rules → Rulesets → Branch rules → Require status checks to pass → No required checks
