Since the revoke command can also be used with certificates that have been installed somewhere else or certificates that have been generated using the --signcsr command it would be a bit complicated to do this, and in some rare cases it may even break something. Also I don't really see a requirement for this, if you are revoking cert.pem and running the script again it will notice the cert missing, will sign it again, and will rotate all other files as well.
@lukas2511 commented on GitHub (Dec 18, 2016):
Since the revoke command can also be used with certificates that have been installed somewhere else or certificates that have been generated using the `--signcsr` command it would be a bit complicated to do this, and in some rare cases it may even break something. Also I don't really see a requirement for this, if you are revoking cert.pem and running the script again it will notice the cert missing, will sign it again, and will rotate all other files as well.
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 @gertcuykens on GitHub (Jul 5, 2016).
If one of them is being revoked all three of them are invalid.
@lukas2511 commented on GitHub (Dec 18, 2016):
Since the revoke command can also be used with certificates that have been installed somewhere else or certificates that have been generated using the
--signcsrcommand it would be a bit complicated to do this, and in some rare cases it may even break something. Also I don't really see a requirement for this, if you are revoking cert.pem and running the script again it will notice the cert missing, will sign it again, and will rotate all other files as well.