Rewrite readme with clearer descriptions

[gilescope]

Have been having a go again at https://github.com/InvArch/INV4-Git . Got much further this time.
(btw had to add the wasm32 target manually - that's worth adding into your scripts if possible)

Got up to:
git push origin master (ideally this should be main)

Now I get Enter your private key/seed phrase:. Is this expected? Is this because I'm usign gpg / yubikeys to sign my commits? I did try doing the same with an unsigned commit but it still popped up for me (I set git config commit.gpgsign false for that repo). Obviously it would be great if signed commits just worked - my ubikey should flash when the git push origin master is executed. I do accept that not everyone signs their commits at the moment but crypo is cool.

[arrudagates]

This is supposed to take your Tinkernet account, as it needs to sign the NFT mint transactions under your account. This authentication flow is also implemented following git standards, if you have a git credential helper set up that stores your credential it will get stored (encrypted with the password you provided on top of whatever encryption your helper of choice uses), and if you don't use a helper to store, it won't get stored.

[gilescope]

Ah, I think the readme could be a little clearer around this bit so we know where to get the key from.

…

On Sun, 18 Sep 2022 at 14:55, Gabriel Facco de Arruda < ***@***.***> wrote: This is supposed to take your Tinkernet account, as it needs to sign the NFT mint transactions under your account. This authentication flow is also implemented following git standards, if you have a git credential helper set up that stores your credential it will get stored (encrypted with the password you provided on top of whatever encryption your helper of choice uses), and if you don't use a helper to store, it won't get stored. — Reply to this email directly, view it on GitHub <#27 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGEJCHSKZ7RZFXDXE6X7ZLV64NO5ANCNFSM6AAAAAAQPMOSSY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[arrudagates]

Good point, I'm repurposing this issue for that.