hy
hy copied to clipboard
GitHub Actions for stale issues/PRs and package deployment
Should we try setting up GitHub Actions for PyPi deployment and automatically managing stale issues and PRs?
PyPI deployment could be a small convenience. Closing old issues and PRs automatically, on the other hand, seems unwise.
We could exclude issues marked as bugs, I believe.
Automatic upload to PyPI is probably a little too dangerous, because you're not supposed to delete published packages or versions, so it would be bad to need to clean up after a mistake.
Having a dedicated develop
branch and only auto upload on merge to master
is a pretty standard CI/CD setup
@brandonwillard I'm not sure it quite makes sense to reopen a two-year-old issue asking for old issues to be closed.
@brandonwillard I'm not sure it quite makes sense to reopen a two-year-old issue asking for old issues to be closed.
This issue isn't "asking for old issues to be closed"; it's asking if we want to set up some fairly standard project management automations.
Isn't the fairly standard project management automation in question to close old issues?
Like, I thought that by "managing stale issues and PRs", you meant closing them, but you tell me.
After a year, no answer seems forthcoming. I'm still skeptical that what small convenience would be obtained by automatically closing inactive pull requests would be worth the bother, and automatically making releases or closing issues is just dangerous, so let's put this to bed.