To make it overcomplicated for git just to fake a point doesn't do it for me.
I am yet to see a real value to use JJ. Those kind of built-up posts I am seeing about JJ on HN tend to push me in the opposite direction.
1) do your test in your current branch, it's related to what you are doing.
2) commit, co master, co -b newtestbranch, PR it, merge in your branch after. You're going to squash rebase at the end anyway...
Real people in the real world (not imaginary people in a fictional blog story) don't overthink every word someone is saying.
Asking for "advices" or asking for "permissions" or just - plain asking - is all the same. People don't see the difference, no one is imagining a scenario based on how the question has been asked, people are probably not even going to remember...
I've just made a test: multiple accounts using the same account/email and there is no conflict.
I even have a matching icon of the issuer for each entry; the issuer is registered for each entry.
I am using the MS Authenticator for years and I've never had any problem of that sort, and of course, I am always using the same email as my account/username.
Anyway, I'm just putting the result of my test. It's not like this going to change your mind about the authenticator or Microsoft itself here...
I am yet to see a real value to use JJ. Those kind of built-up posts I am seeing about JJ on HN tend to push me in the opposite direction.
1) do your test in your current branch, it's related to what you are doing. 2) commit, co master, co -b newtestbranch, PR it, merge in your branch after. You're going to squash rebase at the end anyway...