Skip to content

Releases: hallettj/git-format-staged

v3.1.1

27 Feb 19:06
a4c636c
Compare
Choose a tag to compare

3.1.1 (2024-02-27)

Bug Fixes

v3.1.0

25 Feb 23:36
d183425
Compare
Choose a tag to compare

3.1.0 (2024-02-25)

Bug Fixes

  • disable external diff tools when generating diffs (#77) (28455e6)

Features

  • add --verbose option to git-format-staged (#86) (6b7ae93)

v3.0.0

20 Mar 21:40
b4ed564
Compare
Choose a tag to compare

3.0.0 (2022-03-20)

Bug Fixes

  • prevent colored diff settings from interfering (#65) (53337d9)

Features

  • output info messages ("Reformatted x with y") to stdout instead of stderr (#52) (df1511a)
  • switch executable command to python3 (#72) (b4ed564), closes #67

BREAKING CHANGES

  • git-format-staged now runs with python3 instead of python. You will need to have python3 in your executable path.

v2.1.3

14 Dec 15:59
8e98ce7
Compare
Choose a tag to compare

2.1.3 (2021-12-14)

Bug Fixes

  • remove uses of outdated --stdin switch from prettier examples (fixes #57) (#60) (8e98ce7)

v2.1.2

10 Jun 20:50
ebc6e34
Compare
Choose a tag to compare

2.1.2 (2021-06-10)

Bug Fixes

  • do not attempt to process symlinks (#51) (ebc6e34)

v2.1.1

06 Jan 16:03
1ca5201
Compare
Choose a tag to compare

2.1.1 (2021-01-06)

Bug Fixes

  • do not write formatting changes if formatter produced empty output (#43) (1ca5201)

v2.1.0

27 Jul 23:26
Compare
Choose a tag to compare

2.1.0 (2018-07-27)

Features

  • replace occurrences of {} in formatter command with filepath (e986b4d)

v2.0.0

11 Jun 15:21
Compare
Choose a tag to compare

2.0.0 (2018-06-11)

Features

  • add support for negated file patterns (840f05c)

BREAKING CHANGES

  • The use of '!' to indicate a negative file pattern
    means that files whose names begin with a literal '!' cannot be
    referenced literally in the file pattern list. One possible workaround
    is to use the single-character wildcard ('?') in place of '!' in file
    patterns.

v1.1.0

03 Jun 17:48
Compare
Choose a tag to compare

1.1.0 (2018-06-03)

Features

  • add --no-write option which skips applying formatting changes (418c847)

v1.0.0

27 May 21:11
Compare
Choose a tag to compare

1.0.0 (2018-05-27)

Features

  • accept file pattern arguments as fnmatch globs (ded6e95)
  • change argument structure to catch more errors (90997d8)

BREAKING CHANGES

  • argument structure has been entirely changed.

Changes resulting from formatting are now applied to working tree files
by default. Use the new --no-update-working-tree flag to disable that
behavior. The old --update-working-tree flag has been removed.

The formatter command is now given with a flag (--formatter or -f)
which is required. The command must be quoted if it includes arguments.
The command will be evaluated in a shell, once for each file to be
formatted.

The --glob flag has been removed. Files are now given as one or more
positional arguments. The recommendation is to provide one or glob
arguments to be expanded by the shell evaluating the git-format-staged
command. Glob arguments must be quoted - git-format-staged no longer
expands globs internally. Another option is to list specific files on
the command line.