Skip to content

Conversation

@intgr
Copy link
Contributor

@intgr intgr commented Dec 8, 2023

I have made things!

Motivated by examples like #518, #508 and many others. It happens every few weeks that a change in django-stubs also requires followup changes in djangorestframework-stubs.

Currently, I only find out when someone opens a PR against DRF-stubs and then CI fails. Having scheduled CI would help me be more proactive about these.

Alternatively, we could also change django-stubs CI to automatically trigger workflow_dispatch in DRF-stubs repo on every merge to master. But that would have more moving parts. I think daily schedule is good enough for the time being.

@intgr
Copy link
Contributor Author

intgr commented Apr 23, 2024

@sobolevn This would be useful. It bit us again, ref: #596

@sobolevn sobolevn merged commit a472d34 into typeddjango:master Apr 24, 2024
@sobolevn
Copy link
Member

The next step is to open issues when it fails: see https://github.com/python/typeshed/blob/29db988c0a7c7784782fd28e2e250ba852e3fb72/.github/workflows/daily.yml#L131

@intgr intgr deleted the run-ci-daily branch April 24, 2024 08:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants