The git2 default-features all have to do with ssh or ssh-keys. Those
require OpenSSL, which seems to be a bit tricky to get to compile
properly when cross-compiling on CI.
Also, since this project does not need those parts of the git2
dependency, we should be able to safely disable those features.
Co-authored-by: Maria Hansson <mariahansson92@hotmail.com>
This change makes `get_main_author` try to fetch `user.name` and
`user.email` from the current repo before falling back to a global
default.
Co-authored-by: Maria Hansson <mariahansson92@hotmail.com>
We currently ensure this by simply overriding any existing template.
This is of course sub-optimal, but the previous recommendation, to
globally set `commit.template` to a relative path would otherwise make
`git commit` crash when run in a repo without first creating that
template file, e.g. by running `git mob ...` or `git solo` in the
project directory before committing anything.
This way, we don't have to globally set `commit.template`, and git-mob
will still work.
This change allows the `-o <initials>` flag to override who the main
author of any commits in this repo will be going forward.
What this actually does, is that it modifies the Repository's config
file to change the `user.name` and `user.email` like this.
Running `git mob -o ae be` (given the corresponding authors have been
configured using `git add-coauthor`) is equivalent to doing:
git config user.name "Alice Example"
git config user.email "alice@example.com"
git mob be # be being the initials of "Bob Example" <bob@example.com>
It can:
* Parse the `~/.git-coauthors` file
* List available co-authors with --list
* Filter available co-authors given a list of initials, giving an error
if no co-author matches a given initial
`git-solo` clears the `.git/.gitmessage` commit message template in the
current git repository.
If the current working directory is not within a git repository, it will
print `Not in a git repository` on stderr and exit.
Martin Frost
Martin Frost