v0.1.2

CommitRocket 0.1.2

This release fixes a problem that could leave your large files unusable after
using Git LFS, and it includes the fixes and security improvements from 0.1.1.
Upgrading from 0.1.0 is recommended.

Highlights

Large files now stay usable after --use-lfs

Previously, --use-lfs stored the LFS settings only for the duration of the run.
If you later pulled, reset, switched branches or cloned the repository, your
videos and other big files could turn into tiny text placeholders, and apps
reported them as corrupt or having an invalid extension.

Now --use-lfs saves the LFS rules in the repository (in .gitattributes, one
rule per file type such as *.mp4), so every checkout and clone gets the real files.

• This is the default. Nothing extra is needed.
• All files of a covered type go through LFS from then on, including small and
  future ones.
• To get the old behaviour, use --no-lfs-commit-rules. Checkouts and clones
  will then contain placeholders instead of the real files.
• --lfs-commit-rules is still accepted and does nothing extra.
• Make sure .gitattributes has no uncommitted changes before you run.

Already affected? If your files are already placeholders, add the rules for
your file types to .gitattributes (for example
*.mp4 filter=lfs diff=lfs merge=lfs -text), then run
git lfs install --local and git lfs pull to restore the real files.

Fixed (0.1.1)

• Runs with thousands of files no longer fail on Windows with
  "The filename or extension is too long".

Security (0.1.1)

• A settings file found inside a repository can no longer turn on --force,
  change the remote or branch, write reports or logs, or read pattern files.
  Use --config to set these.
• File names containing characters like [ or * are matched literally, so
  they no longer pull other files into a batch.
• --remote and --branch values that look like Git options are rejected.
• Passwords in remote URLs are hidden in logs, errors and reports. Log and
  report files are readable only by you.
• File names containing line breaks are refused when creating LFS rules.
• Square brackets in file names and Git messages no longer break or hide output.

Other changes

• Releases are published to PyPI using trusted publishing instead of a stored
  token.
• The PyPI page now shows keywords, categories and project links.
• Added issue and pull request templates, a security policy, a code of conduct
  and contributing guidelines.
• Dependabot keeps dependencies, GitHub Actions and pre-commit hooks up to date.

Upgrading

pip install --upgrade commitrocket

What's Changed

• Commit LFS rules by default with --use-lfs (0.1.2) by @coldsofttech in #4

Full Changelog: v0.1.1...v0.1.2