Is it possible to fix blue commits issue without revealing our email address?

[dikiprawisuda]

Hello! Thank you for your hard work.

I'd like to clarify something about the blue commits fix described at:
https://gitsync.viscouspotenti.al/wiki/troubleshooting#blue-commits

It says:

To fix this:
Disable "Keep my email addresses private" in your GitHub settings.

or alternatively:

1. Change the Author Email in the app to your correct, public GitHub email.
2. Back up your locally committed changes (e.g., copy changed files manually).
3. Perform a Force Pull to remove the incorrect commits from the local history.
4. Reapply your backed-up changes.
5. Commit and Sync again. This time, the commits should appear normal and push successfully.

Step 1 of the alternative method says to change the "Author Email" in the app to your correct, public GitHub email. However, we chose this alternative method specifically because we did not want to make our email public. Do we still need to disable "Keep my email addresses private" even when using the alternative approach?

My question is: Can we fix the blue commits issue without revealing our GitHub email?

[ViscousPot]

Yeah, the public GitHub email that is being referred to there is the one generated by GitHub that is somewhat randomised and isn't the same as your login email. If I remember correctly, it should appear by the "Keep my email addresses private" setting and look like 123+something@users.noreply.github.com