We should create an automated PR bot that watches for releases and makes a PR automatically if it detects a change.
I can see two fairly simple ways of doing this:
Run tox -e update and see if git diff shows any substantive change (depending on how #5 is resolved update.py may end up "resetting" all non-IANA version components even if the version hasn't changed).
Change update.py to store a hash of the most recent tarball(s) somewhere in the repository and generate a PR whenever that changes.
I think the biggest challenge is preventing it from generating multiple PRs if it is triggered more than once before the first one is merged, which requires maintaining some state somewhere. Possibly that's easy enough to do because presumably the bot needs its own fork of the repository (or a branch on the main repository), and if the branch name is the same as the IANA version we can just not create the PR if the branch exists.
The text was updated successfully, but these errors were encountered:
We should create an automated PR bot that watches for releases and makes a PR automatically if it detects a change.
I can see two fairly simple ways of doing this:
tox -e updateand see ifgit diffshows any substantive change (depending on how #5 is resolvedupdate.pymay end up "resetting" all non-IANA version components even if the version hasn't changed).update.pyto store a hash of the most recent tarball(s) somewhere in the repository and generate a PR whenever that changes.I think the biggest challenge is preventing it from generating multiple PRs if it is triggered more than once before the first one is merged, which requires maintaining some state somewhere. Possibly that's easy enough to do because presumably the bot needs its own fork of the repository (or a branch on the main repository), and if the branch name is the same as the IANA version we can just not create the PR if the branch exists.
The text was updated successfully, but these errors were encountered: