You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a package that is a GitHub Action as well as a pre-commit hook. So it updates in minor version v0.1.0 and has a major version tracking it v0 which will update automatically on tag. For the purpose of GitHub actions this is what I want as I can do paddyroddy/my-action@v0. But for the pre-commit hook I want to point to v0.1.0 and when I run pre-commit autoupdate it should go to v0.2.0, not v0 (as mutable reference error will happen). But this is what occurs when I run pre-commit autoupdate.
I tried the minor versions to be without v, i.e. 0.1.0 & v0. As well as v0.1.0 & 0 and that approach worked the same as if both had the v in front.
pre-commit --version
3.5.0
The text was updated successfully, but these errors were encountered:
My bad I found #2311. When I run git describe FETCH_HEAD --tags --abbrev=0 on https://github.com/paddyroddy/.github I get v0.34.0. So why does it go to v0 when running pre-commit autoupdate?
search you tried in the issue tracker
autoupdate major
describe your actual problem
I have a package that is a GitHub Action as well as a
pre-commit
hook. So it updates in minor versionv0.1.0
and has a major version tracking itv0
which will update automatically on tag. For the purpose of GitHub actions this is what I want as I can dopaddyroddy/my-action@v0
. But for thepre-commit
hook I want to point tov0.1.0
and when I runpre-commit autoupdate
it should go tov0.2.0
, notv0
(as mutable reference error will happen). But this is what occurs when I runpre-commit autoupdate
.I tried the minor versions to be without
v
, i.e.0.1.0
&v0
. As well asv0.1.0
&0
and that approach worked the same as if both had thev
in front.pre-commit --version
3.5.0
The text was updated successfully, but these errors were encountered: