$ brew info git-team

Warning: Calling `cellar` in a bottle block is deprecated! Use `brew style --fix` on the formula to update the style or use `sha256` with a `cellar:` argument instead.
Please report this issue to the hekmekk/git-team tap (not Homebrew/brew or Homebrew/core), or even better, submit a PR to fix it:
  /usr/local/Homebrew/Library/Taps/hekmekk/homebrew-git-team/Formula/git-team.rb:11

hekmekk/git-team/git-team: stable 1.5.3, HEAD
Manage and enhance `git commit` messages with co-authors
https://github.com/hekmekk/git-team
/usr/local/Cellar/git-team/1.5.3 (7 files, 4.7MB) *
  Built from source on 2021-04-20 at 15:46:22
From: https://github.com/hekmekk/homebrew-git-team/blob/HEAD/Formula/git-team.rb
==> Dependencies
Build: go ✔
==> Options
--HEAD
	Install HEAD version

The use of cellar in the Taps/hekmekk/homebrew-git-team/Formula/git-team.rb is causing the warning:

  bottle do
    cellar :any_skip_relocation
  end

Bug Report

git-team version: 1.3.4
go version: 1.12

failure description

The git config option core.hooksPath is overriden on enable and then unset on disable. If it was set before, the respective hooks will be deactivated when git-team is enabled and not re-enabled when git-team is disabled again. This is confusing for users.

expected behaviour description

Existing hooks in core.hooksPath – apart from prepare-commit-msg – should be respected.

Bug Report

git-team version: 1.7.0
go version: 1.17.7

failure description

Invoking git team assignments add noujz "Mr. Noujz <[email protected]>" exits with error: exit status 255 if no $HOME/.gitconfig is present.
This also happens if the file is read-only.

Background:
It's possible to store gitconfig under $XDG_HOME, e.g. $HOME/.config/git/config
Git checks a set of paths for configurations on every invocation.

expected behaviour description

Creation of $HOME/.gitignore or another distinct file for git-team.
Alternatively or additionally a graceful exit with an explanation error message or offering to create a .gitconfig.

Note: Some approaches like home-manager favours immutable configuration, meaning that wherever gitconfig is put it is read-only by default. That's not always a given and it's possible to make them writeable as well.

PS:This also happens for other git-team cmd's that rely on the existence of the file like git-team disable.

Bug Report

git-team version: 1.7.0
go version: 1.18

failure description

When attempting to install git-team via homebrew, the go build step fails because of outdated dependencies.

expected behaviour description

git-team should install successfully

While installing with --HEAD works, it also brings in other code changes.

proposed workaround:

1. create a new branch off the v1.7.0 commit
2. apply this patch, which fixes the build issues
3. tag the commit with v1.7.1
4. update the homebrew formula to v1.7.1
5. on the main branch, bump the dev version up to 1.7.2-alpha1 or whatever

Hi @hekmekk,

in version 1.5.5 there seems to be an invalid verson in the control file:

dpkg: error processing archive /var/cache/apt/archives/git-team_v1.5.5_amd64.deb (--unpack):
 parsing file '/var/lib/dpkg/tmp.ci/control' near line 2 package 'git-team':
 'Version' field value 'v1.5.5': version number does not start with digit
Errors were encountered while processing:
 /var/cache/apt/archives/git-team_v1.5.5_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

apt policy git-team output is:

git-team:
  Installed: 1.5.4
  Candidate: v1.5.5
  Version table:
     v1.5.5 500
        500 https://apt-sourc.es/deb/hekmekk/git-team stable/main amd64 Packages
 *** 1.5.4 500
        500 https://apt-sourc.es/deb/hekmekk/git-team stable/main amd64 Packages
        100 /var/lib/dpkg/status

Tested on Ubuntu 20.10.

Thanks a lot for your work into this project. I ❤️ it!

Feature Request

Please add a changelog in the format described at https://keepachangelog.com/

proposal

current behaviour

no changelog exists, manually have to check al git commit messages

desired behaviour

a changelog can quickly inform you about the changes

use case / why is this important?

quick overview of changes / features / bugfixes
possibility to get a view with all commits between two versions

Please provide compatibility with libgit2-26. Thanks!

Feature Request

Write co-authors in local config and not in global

proposal

current behaviour

global config is written

desired behaviour

write in local config

use case / why is this important?

Oftentimes I forget to use 'git team disable'. If you push private projects without viewing the commit in the editor, the co-authors names and emails may appear on unwanted locations.

Bug Report

git-team version: 1.7.0
go version: 1.17.7

failure description

After using git-team in a repo-local mode via git team config activation-scope repo-local, switching back to global scope doesn't work in case a repo-local git-team state is still present in a repositories./git dir.

git-team status will return the global status, but during a commit the repo local state is getting picked up and the global state is ignored.

expected behaviour description

I would expect that git-team prioritises the config in alignment with the currently used activation-scope.
If this is global, I'd also hope that it would remove any repo local state that could interfere.

Hi,

it seems like the version v1.5.5 is "newer" than "1.7.0" due to sorting characters before numbers.

Maybe deleting the version "v1.5.5" is easy?

~$ apt list --upgradable -a
Listing... Done
git-team/stable v1.5.5 amd64 [upgradable from: 1.7.0]
git-team/stable,now 1.7.0 amd64 [installed,upgradable to: v1.5.5]
git-team/stable 1.6.0 amd64
git-team/stable 1.5.6-rc1 amd64
git-team/stable 1.5.5 amd64
git-team/stable 1.5.4 amd64