# Make one Windows CI job mandatory

**URL:** <https://discuss.python.org/t/make-one-windows-ci-job-mandatory/4047>\
**Category:** Core Workflow\
**Created:** [April 30, 2020, 11:32pm UTC](https://discuss.python.org/t/make-one-windows-ci-job-mandatory/4047 "2020-04-30T23:32:47Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ammaraskar](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/ammaraskar/32/32_2.png) [@ammaraskar](https://discuss.python.org/u/ammaraskar)\
**Post date:** [May 2, 2020, 1:49am UTC](https://discuss.python.org/t/make-one-windows-ci-job-mandatory/4047/6 "2020-05-02T01:49:51Z")

</div>

> [@vstinner](#):
>
> [Steve Dower replied](https://bugs.python.org/issue39837#msg363498):
> 
> > It would make the job definition significantly more complicated, and I don’t want to do that just to work around an issue with github until we’ve got positive confirmation that the behaviour is intentional and won’t change.

For reference, there is an issue on the Github support forums tracking this [community · Discussions · GitHub](https://github.community/t5/GitHub-Actions/Feature-request-conditional-required-checks/m-p/36938#M2735) and so far it seems like the response from 6 months ago was

> Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.

So I think we can safely assume that Github won’t be fixing this themselves any time soon.

There is a workaround someone posted here that might be worth looking at: [community · Discussions · GitHub](https://github.community/t5/GitHub-Actions/Github-actions-and-required-checks-in-a-monorepo-using-paths-to/m-p/34850/highlight/true#M2027)

---

_[View the full topic](https://discuss.python.org/t/make-one-windows-ci-job-mandatory/4047)._