Originally created by @reardonia on GitHub (Apr 24, 2016).
Just a recommendation:
the use of the term "PRIVATE_KEY" is overloaded; change to ACCOUNT_KEY where appropriate, avoid confusion with privkey, PRIVATE_KEY_RENEW, and the like
Originally created by @reardonia on GitHub (Apr 24, 2016).
Just a recommendation:
the use of the term "PRIVATE_KEY" is overloaded; change to ACCOUNT_KEY where appropriate, avoid confusion with privkey, PRIVATE_KEY_RENEW, and the like
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @reardonia on GitHub (Apr 24, 2016).
Just a recommendation:
the use of the term "PRIVATE_KEY" is overloaded; change to ACCOUNT_KEY where appropriate, avoid confusion with privkey, PRIVATE_KEY_RENEW, and the like
@lukas2511 commented on GitHub (Apr 24, 2016):
I agree, changed this in the mentioned commit. Thanks.
@Robby- commented on GitHub (Apr 26, 2016):
How about also changing the default filenames private_key.json/pem to account_key.json/pem while at it?
@lukas2511 commented on GitHub (Apr 26, 2016):
@Robby- I'd like to avoid that since this would silently impact a lot of setups... :-/