This needs to be carefully reviewed because this is a big change.
The issues were on IWC:
For a workflow,
a bump version may hide 1 tool update or multiple tools update. Therefore, if you close a PR that propose you a version that you consider as 'minor' it does not want that you don't want to have new updates for other tools.
skipping versions has no sense. If you do not accept bump to version 0.4, the next bump should still be called 0.4...
I propose here a new strategy:
start from the 'main' branch
try to autoupdate
compare this to the appropriate branch:
if there is an existing PR (opened or closed) this will be the branch dedicated to this REPO upstream
if there is no it will be the 'main' branch
if there is no change, do nothing
if there are changes check if the last commit of the branch dedicated to this REPO is 'planemo-autoupdate'. If it is not the case, just write a comment to the PR saying that there are new changes but this requires to delete the branch to be integrated.
here is maybe the 'dangerous' part, if there was a branch but the last commit is from 'planemo-autoupdate' we ignore the branch on the remote to avoid any conflict.
then we create a branch locally, commit and force push.
update the PR title, reopen the PR if needed, open a new PR if needed.
The consequence of the new strategy will be:
if you want to skip this update but have new updates, close the PR but not delete the branch
if you made a change in the PR but finally you want the last update, close the PR and delete the branch.
if you do not have time to take care of this PR now, the PR will be updated.
This needs to be carefully reviewed because this is a big change. The issues were on IWC:
I propose here a new strategy:
The consequence of the new strategy will be: