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've merged in the latest tags into the default branch so that pre-commit will pick them up. Precommit's behaviour of insisting on using the default branch (which is the one meant for PRs and therefore generally develop or unstable) is unintuitive for me, so I never guessed this would be a requirement! I'll make sure to include merging back into develop as a release checklist item from now on.
I'm using isort with pre-commit, and use the
pre-commit autoupdate
command to update to the latest versions of isort and other tools.However, it's not picking up today's 5.3.1 or 5.3.2. And strangely, if I manually set it to 5.3.2,
autoupate
resets it to 5.3.0.This is because (pre-commit/pre-commit#1555 (comment)):
Would it be possible to tag the default branch, or merge the tags into it so the tools play nicely with each other?
It's great to see regular releases here, and thank you for all your work!
The text was updated successfully, but these errors were encountered: