But, every launch you will be asked to authorize yourself with simple instructions to avoid the limit, once you authorize, it will store token in secure keyring and stop asking.
This is unnecessary, because the readme already talks about the benefits of authenticating and what will happen if the user won't authenticate.
Instead, I recommend creating a command like mmc-export gh-login which will do it when the user requests that. Similarly, mmc-export gh-logout.
Edit: As of 2.2.1 it seems the script won't continue at all until I do authenticate with GitHub 😢
This is unnecessary, because the readme already talks about the benefits of authenticating and what will happen if the user won't authenticate.
Instead, I recommend creating a command like
mmc-export gh-login
which will do it when the user requests that. Similarly,mmc-export gh-logout
.Edit: As of 2.2.1 it seems the script won't continue at all until I do authenticate with GitHub 😢