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-hooks
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v3.1.0
Choose a base ref
...
head repository: pre-commit/pre-commit-hooks
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v3.2.0
Choose a head ref
  • 12 commits
  • 32 files changed
  • 5 contributors

Commits on May 20, 2020

  1. Don't use LocalPath.strpath

    mxr committed May 20, 2020

    Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    Copy the full SHA
    f35bfed View commit details
  2. Merge pull request #488 from mxr/strpath

    Don't use LocalPath.strpath
    asottile authored May 20, 2020

    Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    Copy the full SHA
    0e509dd View commit details

Commits on May 27, 2020

  1. Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    Copy the full SHA
    1da4a7f View commit details
  2. Merge pull request #491 from pre-commit/all-repos_autofix_faster-tests

    slightly speed up tests by avoiding pre-commit install
    asottile authored May 27, 2020

    Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    Copy the full SHA
    f0bf512 View commit details

Commits on Jun 17, 2020

  1. Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    Copy the full SHA
    c14b3aa View commit details

Commits on Jun 19, 2020

  1. Document the default always_run behaviour of no-commit-to-branch

    Include instructions on how to use files/types/excludes/exclude_types
    with the no-commit-to-branch hook, along with the caveat of it allowing
    empty commits
    mjay-taskize committed Jun 19, 2020

    Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    Copy the full SHA
    b469434 View commit details
  2. Merge pull request #501 from marcjay/document-no-commit-to-branch-alw…

    …ays-run
    
    Document the default always_run behaviour of no-commit-to-branch
    asottile authored Jun 19, 2020
    Copy the full SHA
    f7dd0c0 View commit details

Commits on Jul 1, 2020

  1. Copy the full SHA
    53a05b9 View commit details

Commits on Jul 2, 2020

  1. Merge pull request #502 from jgeerds/feature/catch-pydevd-pycharm-deb…

    …ug-statement
    
    debug-statements: Add "pydevd_pycharm" to list of debug statements
    asottile authored Jul 2, 2020
    Copy the full SHA
    5372f44 View commit details

Commits on Jul 30, 2020

  1. Fix parsing of git output with unusual characters

    On Windows, all files are "executable".
    Therefore, to know if a file is supposed to be executed,
    we check how its attributes were recorded by git:
    we run a `git ls-files` command in a subprocess.
    
    By default, this command outputs information
    on multiple lines (file and their data separated by newlines).
    When a file contains an unusual character,
    the character is escaped with an integer sequence
    (such as `\303\261`), and git wraps the whole filename
    in double-quotes because of the backslashes.
    It breaks the current code because we try to open
    the filename containing the double-quotes:
    it doesn't exist, of course.
    
    Instead of trying to fix this special case by removing
    the double-quotes, and breaking other cases
    (a double-quote is a valid filename character on Linux),
    we tell git to separate each item with the null character `\0`
    instead of a new line `\n`, with the option `-z`.
    With this option, git doesn't escape unusual characters
    with integer sequence, so the output is fixed, and we
    parse it by splitting on `\0` instead of `\n`.
    
    Fixes #508.
    pawamoy authored and asottile committed Jul 30, 2020
    Copy the full SHA
    4faed34 View commit details
  2. Merge pull request #509 from pawamoy/patch-1

    Fix parsing of git output with unusual characters
    asottile authored Jul 30, 2020
    Copy the full SHA
    9eab799 View commit details
  3. v3.2.0

    asottile committed Jul 30, 2020
    Copy the full SHA
    e1668fe View commit details
Loading