GitoxideLabs/gitoxide v0.20.0

on GitHub

This release also fixes compatibility issues that formerly prevented to fetch or clone form https://googlesource.com.

Changed

• represent GIT_(COMMITTER|AUTHOR)_(NAME|EMAIL|DATE) with git configuration.
  That way it becomes more obvious where values are coming from.

New Features

• auto-enabled verbosity for gix fetch/clone and add --no-verbose.
  I found myself always adding (and having to remember to add) the -v flag
  for long-running operations so these should be able to default to a
  higher verbosity level.

  To counter that, there is a new --no-verbose flag to turn that off.

• add --strict option to enforce strict checking of configuration.

• gix odb stats to calculate statistics on the object database.
  This includes the amount of objects along with a listing of where they are
  located.

• gix clone --no-tags support.
  This is the same as git clone --no-tags.

Changed (BREAKING)

• open::ReplacementObjects is removed in favor of two custom git-configuration flags.
  Now it's possible to map the environment variables GIT_REPLACE_REF_BASE and GIT_NO_REPLACE_OBJECTS
  to custom git configuration keys which can also be set, namely gitoxide.odb.replaceObjectsRefBase
  and gitoxide.odb.noReplaceObjects.

  Along with the possibility of disabling the usage of GIT_ prefixed environment variables one
  reaches the previous level of control without making object replacement a special case.

New Features (BREAKING)

• represent object cache configuration like GITOXIDE_PACK_CACHE_MEMORY in git-configuration.
  That way there is a unified system for how to set values, which may be overridable by configuration
  variables or not.

  With this changes, the explicit application of environment variables for setting the cache
  isn't required anymore as everything happens using git-configuration, and automatically,
  while providing full control like before.

Commit Statistics

• 21 commits contributed to the release over the course of 30 calendar days.
• 30 days passed between releases.
• 7 commits were understood as conventional.
• 0 issues like '(#ID)' were seen in commit messages

Commit Details