git_curate changelog

Changelog History

Page 1

• v1.1.1 Changes

  • ⬆️ Dependency version upgrades

• v1.1.0 Changes

  🔄 Change that may be breaking for an obscure use case

  • Output more helpful message in case there are no deletable branches when git curate run without -l/--list flag.

  This will be a breaking change but only in the unlikely event that the output of git curate is being piped through or processed by another program when run in interactive (non---list) mode.

  🆕 New behaviour when there are no deletable branches: Outputs There are no local branches that can be deleted.

  Old behaviour when there are no deletable branches: Outputs (irrelevantly and confusingly) the legend of interactive commands, followed by the message No branches deleted.

• v1.0.2 Changes

  • 🛠 Fix incorrect status-vs-upstream when commit subject begins with square-bracket-enclosed string.

• v1.0.1 Changes

  • 🛠 Fix fatal: bad revision '+' error on encountering multiple worktrees.

• v1.0.0 Changes

  • ✂ Remove support for Ruby < v2.4.9.

• v0.8.0 Changes

  • 🔄 Change options to make them more memorable/obvious
  • 🖨 Always print options legend at top, if in interactive mode
  • ➕ Add a column showing last commit hash
  • 👉 Tweak column header layout
  • 🛠 Fix warnings on Ruby 2.7
  • 🛠 Fix minor error in README

• v0.7.5 Changes

  • ⬇️ Drop support for Ruby 2.1
  • ⬆️ Dependency version upgrades

• v0.7.4 Changes

  • ⬆️ Dependency version upgrades

• v0.7.3 Changes

  • ✂ Remove blank vertical gutters either side of output table
  • ⚡️ Dependency versions updated

• v0.7.2 Changes

  • 👀 Nicer error messages; for example, if git curate is run outside of a git repo, the user will now see the same error message as they would see from running git branch (as opposed to seeing an unsightly stack trace)
  • 🐎 Performance improvements: it now runs faster, as the number of system calls made by the application is reduced
  • 👌 Improvements to code structure and internal documentation

• 1
• 2
• 3
• Next ›
• Last »