Comparing pre-commit:main...bbannier:main · pre-commit/pre-commit · GitHub
Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: pre-commit/pre-commit
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: bbannier/pre-commit
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 1 commit
  • 3 files changed
  • 1 contributor

Commits on Nov 8, 2024

  1. Fix autoupdate to not switch to completely different tags 

    If multiple tags to the release of a hook `pre-commit autoupdate` would
previously pick the first tag, possibly non-deterministically
depending on a locally configure Git `tag.sort` configuration. If
multiple tags point to the release hook release, e.g., if multiple
projects are tracked in the same repo, this could cause switching to a
different projects tag. At the very least this introduces churn and
makes it hard to see what version was upgraded to, and worst case could
cause `pre-commit autoupdate` behave differently on different machines.

With this patch we always prefer to pick the tag which shares the longest
prefix with a currently configured tag.

Closes #3349.
    @bbannier
    bbannier committed Nov 8, 2024
    Configuration menu
    Copy the full SHA
    93d8ebf View commit details
    Browse the repository at this point in the history
Loading