question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

GitHub Enterprise repos need their own e-mail setting or default of LDAP account email

See original GitHub issue

Description

I have repos that I use/contribute to via this GitHub.com account. I also have GitHub repos that I use via my corporate GitHub Enterprise account which uses a completely different e-mail address than my regular GitHub.com account (business is business and my other stuff isn’t business).

However, the GH Desktop client seems to default everything to my personal e-mail address (associated with this account) – including the GitHub Enterprise connections. So all of my commits are now attributed to a different user/e-mail that doesn’t exist on GH Enterprise. Being I don’t have access to add any additional (read: non corporate) e-mail addresses to my GH Enterprise account, I can’t do the “easy” solution to have those commits tied to my account via additional e-mails.

It would be super awesome if there was a way to configure GH Dekstop to automagically use a specific e-mail/account for GH Enterprise repos. Specifically it should default to LDAP Sync’d e-mail assigned to your account. This would also prevent the problem when one uses their username based e-mail address rather than their marketing friendly name based e-mail address: myCrpyticUserName@company.com VS Firstname.Lastname@company.com

LDAP sync to GH Enterprise thinks I’m Firstname.Lastname@company.com, but I login with and basically exclusively use myCrpyticUserName@company.com. So this is a bit confusing for me as a user to try to fix things (not due to GHE or desktop, but to how my company has things configured). So some sort of “default” email for GHE as mentioned above would fix/prevent such confusion.

The current issues has been resolved going forward (at the moment at least) with “git config user.email” and historically with “Changing author info” – thanks for the solid knowledge base BTW – but when I inevitably get a new workstation or blow up my current OS and reinstall, I’m going to totally forget to run the one time git config user.email and I’m going to have to do this again… Please save me from my own forgetfulness.

Version

GitHub Desktop version: 1.0.0

OS version: Windows 10 Enterprise 1703 64 Bit

Steps to Reproduce

  1. Login via desktop to both GH and GH Enterprise using different accounts/emails for each (it’s extremely likely that I logged into GH first, but I’m only like 99.99999% positive of that)
  2. Commit something to GH Enterprise
  3. See that commit was not attributed to your GH Enterprise user

Expected behavior: Commits should always be attributed to the GH Enterprise user when committing to a GH Enterprise repo. If committing to DIFFERENT GH Enterprise servers/repos with DIFFERENT accounts, use the correct account accordingly.

Actual behavior: Standard GH account is used for the commit.

Reproduces how often: every time until you fix with git config user.email

Edit: Finished some thoughts, and corrected some typos. Nothing major.

Issue Analytics

  • State:open
  • Created 6 years ago
  • Reactions:2
  • Comments:6 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
Seb33300commented, Oct 16, 2018

Maybe a new tab could be added to the repository settings panel to configure name and email to use for the repository (leave blank to use default configured in global options).

This tab could be a way to display / edit values from

git config --local user.name
git config --local user.email
2reactions
iAmWillShepherdcommented, Sep 21, 2017

Thanks so much for your feedback @kmscode . This seems like something a lot of other people can benefit from as well!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Integrate LDAP with GitLab
LDAP users with the same email address can share the same GitLab account. Configure LDAP. To configure LDAP integration, add your LDAP server...
Read more >
Configuration - Gerrit Code Review
If set, Gerrit trusts and enforces the user's e-mail using the HTTP ... Only the LDAP password is allowed when doing Git over...
Read more >
Configuring Authentication Settings | TeamCity On-Premises ...
LDAP Integration allows setting LDAP property to get TeamCity username from user's LDAP entry. Modules, corresponding to Git hosting providers, ...
Read more >
Azure AD SSO integration with a GitHub Enterprise Cloud ...
mail, so you need to edit the attribute mapping by clicking on Edit icon and change the attribute mapping. Screenshot that shows the...
Read more >
GitHub Organizational Data - Backstage.io
Importing users and groups from a GitHub organization into Backstage. ... It also relies on the user having configured such an email in...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found