Closed (fixed)
Project:
Drupal.org infrastructure
Component:
Git
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
25 Apr 2020 at 20:04 UTC
Updated:
11 May 2020 at 17:29 UTC
Jump to comment: Most recent
I have just created a project at https://www.drupal.org/project/ex_icons but I have just noticed that two of the most recent commits on the 8.x-1.x release branch have incorrect commit author information.
Would it be at all possible for someone to either roll back the branch two commits, or delete the release so I can re-push the commits with the correct author, or something else to solve this mistake I made?
Any help is appreciated, thanks!
Comments
Comment #2
avpadernoThe commits aren't associated with the account because the email used for the commits isn't one of the email shown in https://www.drupal.org/user/3055747/edit/email-addresses. You need to add the email in that page, to avoid that happens in the future.
Comment #3
avpadernoAs for associating the past commits to your account, once you have added the email to your account, an administator can fix the commits.
Comment #4
wongjn commentedThank you for your response. I have now set and confirmed the alternative email address to my account.
Please can an administrator fix the commits such that the author is consistent with the other commits.
Comment #5
drummDone!
Comment #6
wongjn commentedSorry, it seems I may been unclear.
I'd like the commits for
552b948fandd6fa5573to have author and committer changed to name wongjn and email to SaltPacket@3055747.no-reply.drupal.org.They incorrect commits are currently associated to my Drupal account because I have temporarily added the incorrect git email to my account, but I would like to remove it again once resolved.
Comment #7
drummWe generally do not support rewriting Git history for release branches. When you need to use a dev release, many people pin to specific commit hashes; so changing them causes confusion when a commit hash effectively disappears. And anyone else with a Git clone of the project may have extra steps to pull in rewritten remote history.
If this is a privacy concern, and you understand the drawbacks, we can spend a bit of time to manually bypass this. If this is necessary, go ahead and push the corrected commits to a separate branch.
Comment #8
wongjn commentedOK, understood. I thought it might have been OK to rewrite the git history since the project was only created and pushed several days ago. We'll leave it as is then I guess! Thank you for the help.