You can rewrite the history:
https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History
I personally would make a backup of ma branch (just push it with a
different name), then squash all commit in my current one and amend that
single commit then force push the branch.
Am 24.01.24 um 09:58 schrieb java joe via platform-dev:
Yikes! I did a ton of commits to my fork. I did NOT change the commiter
/ auther field.
How can I fix it so that I dont have a ton of errors in my PR #873.
On 1/24/24 03:52, Christoph Läubrich via platform-dev wrote:
Only the Comitter / Author field must be set to the ECA verified
e-mail address in your commit:
https://docs.github.com/en/get-started/getting-started-with-git/setting-your-username-in-git
Am 24.01.24 um 09:40 schrieb java joe via platform-dev:
I have multiple developer accounts where I do work, most notable is AWS.
I do not have an email account on my Amazon Web Services developer
account.
My ECA I signed with eclipse is via my home account where I get email.
QUESTION: Can I tie the accounts together somehow or do I need to sign
another ECA with eclipse for my commits to be valid when I work via
my AWS account?
Any help greatly appreciated!
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev