'*text' only matches string ended with 'text'. So it matches 'ASCII text',
but does not match 'ASCII text executable'. Before, `git summary
--line` just counts plain text file, now we fix it.
When the last tag is also the last commit, then we need to account
for a much longer tag output:
HEAD, tag: v1.0.1, origin/master, origin/HEAD,...
This fix strips out 'HEAD', the rest is handled by existing code.
When gitflow is used, commits on merged feature branches were
appearing in the generated output with tags labeled as:
origin/feature/BRANCH_NAME
This fix filters out any 'tags' that include forward slashes,
which eliminates this behavior. The commits then appear as part
of the tag they were merged in with.
When hit `git setup` in an empty directory, it doesn't create a commit. But often we need an empty initial commit for future rebasing and reseting, etc. Fixes#318.
git-summary correctly displays project name when not executed in the top
level directory of a repository. Fixestj/git-extras#302.
Uses the git-sh-setup script to find top level directory and then uses
that directory name for the project name.
(1) make format configurable
you can change the default changelog format by configuring
changelog.format git variable
for example:
git config changelog.format '- %s (%ae)'
gives you something like that:
- Merge pull request #298 from timfeirg/master (hemanth.hm@gmail.com)
- remove stuff from readme & form a list (kkcocogogo@gmail.com)
see git-log man for more examples
(2) make log options configurable
set `changelog.opts` to influence the way changelogs are generated
git config changelog.opts --no-merges
or:
git config changelog.opts --first-parent
fixes#285
also:
- delay calculating HEAD until needed
- remove extra line before header
The editor used will be chosen from the GIT_EDITOR environment variable,
the core.editor configuration variable, the VISUAL environment variable,
or the EDITOR environment variable (in that order).
That ensures that `git-changelog` and `git-authors` will use the same editor
as `git-commit`, `git-merge` etc.
This takes any extra arguments supplied to `$git feature` and sets
them as the new feature name. For instances, instead of throwing an
error if `$git feature new thing` is called, it will create branch
`feature/new-thing`.
