ohmyzsh

mirror of https://github.com/ohmyzsh/ohmyzsh.git synced 2026-03-20 03:13:33 +01:00

History

KhasMek 668dc14b28 Plugins: git - be less verbose with commits Remove the -v flag by default with the standard aliases gc, gc!, gca, and gca!, while adding new aliases for those that choose to put the entire diffs in their commit message. In some cases git -v ignores it's rules of cutting everything below the line: # ------------------------ >8 ------------------------ causing the full diff of the commit to be shown in the commit message. This is usually caused by commits that are heavy in shell style comments or mardown files with lots of headers defined (tldr: #'s, bangs). IMHO, and from my understanding of the creators of git and many others - showing a full diff in the commit message not only completely breaks the acceptable/expected format of "good" commit messages, but is also completely redundant and unnecessary. (If you have access to the commit message, more than likely you can access the diff of the commit via a multitude of other methods (CLI tools, GUI tools, web interfaces in a much nicer looking format.)	2015-06-07 11:26:32 -06:00
..
git.plugin.zsh	Plugins: git - be less verbose with commits	2015-06-07 11:26:32 -06:00
README.md	Many updates to git plugin (see #2790 )	2015-05-08 16:00:22 +02:00

KhasMek 668dc14b28 Plugins: git - be less verbose with commits

Remove the -v flag by default with the standard
  aliases gc, gc!, gca, and gca!, while  adding new
  aliases for those that choose to put the entire
  diffs in their commit message.

  In some cases git -v ignores it's rules of cutting
  everything below the line:
  # ------------------------ >8 ------------------------
  causing the full diff of the commit to be shown in the
  commit message. This is usually caused by commits that
  are heavy in shell style comments or mardown files with
  lots of headers defined (tldr: #'s, bangs).

  IMHO, and from my understanding of the creators of
  git and many others - showing a full diff in
  the commit message not only completely breaks the
  acceptable/expected format of "good" commit messages,
  but is also completely redundant and unnecessary. (If
  you have access to the commit message, more than
  likely you can access the diff of the commit via a
  multitude of other methods (CLI tools, GUI tools, web
  interfaces in a much nicer looking format.)

2015-06-07 11:26:32 -06:00

git.plugin.zsh

Plugins: git - be less verbose with commits

2015-06-07 11:26:32 -06:00

README.md

Many updates to git plugin (see #2790 )

2015-05-08 16:00:22 +02:00

README.md

git

Maintainer: @ncanceill

This plugin adds many useful aliases and functions.

Usage

See the wiki for a list of aliases and functions provided by the plugin.