Skip to content

Latest commit

 

History

History
167 lines (67 loc) · 5.01 KB

CHANGELOG.md

File metadata and controls

167 lines (67 loc) · 5.01 KB
Raw

git-redact

Changelog

2/13/14

  1. Add filter settings to .git/config if they're not already there.

2/5/14

  1. Set-up adds .gitattributes if it doesn't already exist.

1/29/14

  1. Add set-up step to read_test, hereafter known as v.2.

  2. First attempt to write confirmations to a file works.

1/20/14

  1. Firing redactions via the smudge filter might work. This would leave git less confused about redacted values in the head not matching the raw values in the working tree.

  2. Rather than identifying and operating on files via git status --porcelain, the redaction routine would run once for every piece of standard input.

11/25/13

  1. When redacting, ignore files that have been deleted from the previous commit.

3/20/13

  1. Every time a file is redacted, its path is added to .redacted_originals/.redacted_files. This file is created automatically if it doesn't exist.

  2. If no redactions are made in any of the updated files, git-redact prints a notification message and the user is not prompted for approval. Fixes issue #5.

  3. Files are only backed up to .redacted_originals if they've been redacted. Fixes issue #4.

  4. Redacting just one file? The confirmation report uses singular language instead of plural.

  5. Works for nested files, not just those in the root.

3/17/13

  1. Updated README with instructions.

3/16/13

  1. If none of the redaction patterns are found and no changes are made in a file, exclude it from the confirmation report. Only print information for files in which changes have been made.

3/14/13

  1. Fixed a huge bug by changing IFS while swap_array is created. This allows the correct storage of patterns that include spaces. Fixes issue #2.

3/5/13

  1. Exits 1 if it can't find patterns to use for redactions. Exits 0 otherwise.

  2. Initialization. Creates .gitredact, .redacted_originals and .gitignore if they don't exist. Exits 1 after creating .gitredact, because the user hasn't yet added patterns to it.

  3. Error and task messages during initialization.

3/3/13

  1. Clears old files and restores originals before starting a new redaction.

  2. Renamed .gitredact-template to .gitredact.

  3. Renamed .gitredact to git-redact. (Git command-style, no longer hidden.)

3/1/13

  1. When the user approves redactions, originals are copied to a .gitignored folder and the redacted versions are renamed in their place.

2/26/13

  1. Creates only one redact.sed file and one swap_array. Closes issue #1.

  2. Confirmation report formatting changes.

2/21/13

  1. Redacts multiple files, and confirms changes made to each file separately.

2/19/13

  1. Patterns that aren't found don't print to the confirmation report.

  2. Instead of appearing many times in the confirmation report, redaction matches are printed only once for all their occurrences.

1/8/13

  1. Confirmation reporting is prettier. If a redaction occurs on more than one line, the line numbers are separated by commas before they're printed in the sentence. The last number is separated from the penultimate number by spaces and the word 'and'.

  2. The odd line break is gone.

  3. More consistent replacement of word boundaries.

1/6/13

  1. As a first step, git-redact tests for the operating system. If it's OS X, it uses that system's ugly word boundary syntax ([[:<:]] and [[:>:]]).

  2. In the confirmation step, git-redact will print the original word boundary syntax as entered by the user.

12/28/12

  1. The test inside replacePatternWithMatch() now uses sed instead of grep.

12/20/12

  1. Before redactions are made, any regex word boundary (\b) matches in swap_array are substituted for the syntax understood by sed in OS X ([[:<:]] and [[:>:]]). Eventually, I'd like to test for the OS and replace this value with the syntax understood by each.

12/11/12

  1. The operations array contains actual line numbers and actual values for every pattern matched during a redaction. This array is used to log results.

12/9/12

  1. Collect all the redact/replace values in an array. Write out two sed files -- one to perform the redactions, and another to collect the line numbers of each transformation.

  2. Added a summary report. After it runs, git-redact will print all its changes to the console and ask the user to approve them before making them permanent.