Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Why would you ever want to share a valid Github API key publicly?


It's been a while, but IIRC it was a key with no permissions used on a CI server to get around github's API usage limits.

It probably wasn't the best idea, but it was the only "secret" needed in the whole project and I didn't want to maintain a way of managing secrets in a public project for a pointless key.

In the end I did just that, and looking back it was the better choice, but at the time it was annoying.


"... used ... to get around github's API usage limits."

I wonder why they'd want to invalidate that. :)


Continuous development, e.g. Jenkins? (Please don’t do this)


Why not?


Out of curiosity, why not a deploy user? https://developer.github.com/guides/managing-deploy-keys/




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: