Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use locally defined email for commits #270

Closed
sorenlouv opened this issue Nov 10, 2021 · 1 comment · Fixed by #307
Closed

Use locally defined email for commits #270

sorenlouv opened this issue Nov 10, 2021 · 1 comment · Fixed by #307

Comments

@sorenlouv
Copy link
Owner

Currently the backport tool uses the globally defined email when for the backport commit. Instead it should use the locally defined email address.

The email address for the local repo can be retrieved with git config user.email and updated with git config --local user.email john.doe@email.co

@raubel
Copy link

raubel commented Feb 2, 2022

Hi,
Why has this issue been closed?
I'd be interested in retrieving user email and username from local branch (or from the user's backport config file), because I don't want to define global git properties to define them.
Is that possible with the current version.

Today, I end up with this error:

remi > backport
? Select commit #506 (4c36bfb6)
? Select branch V5_3
✔ 100% Cloning repository (one-time operation)

Backporting to V5_3:
✔ Pulling latest changes
✖ Cherry-picking: story(API): optimize persist and mass update data request processing (#506)
Cherrypick failed:
Command failed: git cherry-pick -x 4c36bfb653a6b6ad040a3694599274ea62733b9f
Performing inexact rename detection: 100% (409500/409500), done.

*** Please tell me who you are.

Run

  git config --global user.email "you@example.com"
  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got 'remi@remi-example.(none)')

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants