-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run CI on tags #118
Run CI on tags #118
Conversation
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #118 +/- ##
=======================================
Coverage 82.94% 82.94%
=======================================
Files 8 8
Lines 428 428
=======================================
Hits 355 355
Misses 73 73 ☔ View full report in Codecov by Sentry. |
Why don't we have a separate Docs.yml action? There's no need to rerun CI tests on tags, we only need the docs. |
I guess it doesn't hurt to prove that the tests pass specifically for the tag you want. Otherwise if you wanna check you have to go back in time and look for the tests of the associated commit. But I don't feel strongly about either option |
I think it's sufficient to run CI once for every commit. If you go to a tag, you also end up with the commit with the CI runs next to it. |
Alright, I'll split out a docs workflow tomorrow |
Co-authored-by: David Widmann <devmotion@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Hopefully fixes the lack of a stable docs build