Skip to content

access: merge my Gerrit accounts #66778

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

Closed
HeliC829 opened this issue Apr 11, 2024 · 5 comments
Closed

access: merge my Gerrit accounts #66778

HeliC829 opened this issue Apr 11, 2024 · 5 comments
Assignees
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone

Comments

@HeliC829
Copy link
Contributor

HeliC829 commented Apr 11, 2024

I've contributed to golang with the address [email protected] for my CL, and for logging in to Gerrit.

For some reason, going forward, I'll be using the email address [email protected] for logging in to Gerrit. I still intend to contribute to the Go project, for example, do more about my proposal #60072.

@golang/release , Can you merge my Gerrit accounts so that all my change before would still show up as my CL?

Thanks!

@github-project-automation github-project-automation bot moved this to Incoming in Access Apr 12, 2024
@seankhliao seankhliao added this to the Unreleased milestone Apr 12, 2024
@cagedmantis cagedmantis added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Apr 12, 2024
@cagedmantis
Copy link
Contributor

cagedmantis commented Apr 12, 2024

Hi @HeliC829, the most foolproof way of accomplishing this is by adding your email address to the first account https://go-review.googlesource.com/settings/#EmailAddresses

@HeliC829
Copy link
Contributor Author

Hi @HeliC829, the most foolproof way of accomplishing this is by adding your email address to the first account https://go-review.googlesource.com/settings/#EmailAddresses

Oh, I forgot that I can change my email account this way.....but I have already created a new gerrit account with my new email address, so I can't add my new address to my old gerrit account ( it would show "address is in use by another account" ). So what should I do now?

@cherrymui cherrymui moved this from Incoming to Active in Access Apr 19, 2024
@dmitshur dmitshur self-assigned this May 16, 2024
@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels May 16, 2024
@dmitshur
Copy link
Member

In this case, we can merge your two accounts into one. That is done now.

Specifically, both of your emails are now associated with your older Gerrit account (ID 61713, created Mar 10, 2023), https://go-review.googlesource.com/dashboard/61713. The more recent account (ID 3384854, created Apr 6) is considered merged.

You should be able to login and update your emails at https://go-review.googlesource.com/settings/#EmailAddresses to match your new preference. Please comment if something didn't work as expected.

Thanks for contributing to Go.

@github-project-automation github-project-automation bot moved this from Active to Reviewed in Access May 16, 2024
@HeliC829
Copy link
Contributor Author

The CL 584735 and CL 578175 are still under the newer Gerrit account (ID 3384854). Should I submit the CLs again, or just wait for them to be moved to the older Gerrit account (ID 61713)?

@dmitshur
Copy link
Member

dmitshur commented May 17, 2024

Sorry for the trouble, I didn't realize it wouldn't have effect on your newer CLs.

Since it's only two of them and both haven't begun code review yet (and one of them needs a merge conflict resolution), I would suggest closing them and re-sending with your newly merged account. Hopefully that works well, sorry again for the overhead and thanks for bearing with it. (If really needed, we can temporarily unlink the accounts again, but hopefully it's fine to just move forward in this case.)

@golang golang locked and limited conversation to collaborators May 17, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
Status: Reviewed
Development

No branches or pull requests

5 participants