search

PyCQA / docformatter

Formats docstrings to follow PEP 257
https://pypi.python.org/pypi/docformatter
MIT License
530 stars 62 forks source link

Bad tag scheme: pre-commit issue #163

Closed AntoineD closed 1 year ago

AntoineD commented 1 year ago

Hello,

because of the different tag schemes, the 1.6.0 release candidates tags are ordered like (see the tags from the gitub UI):

This seems to be the reason why pre-commit always autoupdates docformatter to 1.6.0.rc1 which is not usable for me.

Would it be possible to get the tag scheme consistent, or may be even better to use branches instead of tags for release candidates?

weibullguy commented 1 year ago

Thanks for this. I didn't even realize I had tagged master with v1.6.0.rc1. I moved that tag (and updated it to the same pattern) to the release/v1.6.0 branch. pre-commit autoupdate should get you v1.5.1 now or right before the release branch if you use --bleeding-edge.

I'm going to leave this open for now in case you run into more problems related to this issue.

AntoineD commented 1 year ago

Hello,

this is happening again: pre-commit autoupdates docformatter to 1.6.0.rc1!

weibullguy commented 1 year ago

@AntoineD sorry. Don't know how that happened, but it's gone again. Now I know how it happened and I fixed it so it won't happen again.