Skip to content

Consider GIT_AUTHOR_EMAIL/GIT_COMMITTER_EMAIL as current author/committer #72

Open
@blueyed

Description

@blueyed

When using $GIT_AUTHOR_EMAIL and $GIT_COMMITTER_EMAIL with something else than git config user.email, it will display a warning:

WARN Will not fix up past commits not authored by you, use --force to override, commit: …

I think that it should consider the env settings as the current owner - not sure if alone or additionally.

(FWIW, I am using the env variables to use different emails per projects.

It is easy enough to configure user.email there additionally, but that might require to do it with many sub-directories / projects for a company stored in a common ancestor dir, where setting the env can be done for all sub-directories more easily)

Metadata

Metadata

Assignees

Labels

upstreamBlocked on upstream libgit2/git2rs

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions