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
Upload NEWS file as artifact #30419
Upload NEWS file as artifact #30419
Conversation
Conflict resolved! Would be nice to get this merged, it'd make reviewing docs PRs much easier: can download the generated files rather than checking out the branch locally and building them manually. |
Conflict resolved! |
(I'm working my way through some PRs which have been approved and are labeled "awaiting merge", hence my seemingly bolt from the blue comment. Why? Read here.) Can this be merged or are you still waiting for @Mariatta and @ezio-melotti to review? |
Do we know how much storage is the python
org using?
I don't expect the NEWS
file to be particularly large, but if it gets generated for each PR it will add up and we might eventually reach the limit. We can also tweak the number of day the artifact is stored before being automatically deleted.
Other than that, the PR LGTM.
The current usage will be visible under https://github.com/organizations/python/settings/billing for org admins. |
Fixes python/core-workflow#147.
Since that issue was opened, we've moved testing from Travis CI to GitHub Actions.
And more recently the blurb tool is now being as part of
make build
called as part ofmake ... doctest
in the "Check documentation" step (#30009).So let's also upload the generated
NEWS
file as an artifact so it can be inspected after the build.For example, it's available to download here: