News for hackers. Stuff that matters.
Re:Read-only deploy keys by philfreo on Tuesday June 16, 2015 @09:59PM (#9729729)
Rather than using Deploy Keys at all it seems completely better in almost every way to create a fake GitHub user and use its account's regular SSH key. You can, using Teams, give that user read-only access to whichever repo(s) it needs access to for deployment.
Re:Read-only deploy keys by baudehlo on Tuesday June 16, 2015 @10:04PM (#9729744)
Github calls these "machine users". But it's more annoying to manage than the deploy keys UI.
Re:Read-only deploy keys by BillinghamJ on Wednesday June 17, 2015 @03:45AM (#9730483)
However Github doesn't actually have support for "machine users" - they're just normal user accounts with full GUI access on Github.com.

And if you are on Github's per-user pricing model, machine users are not free.

Re:Read-only deploy keys by novaleaf on Wednesday June 17, 2015 @08:08AM (#9731226)
This is exactly what I do on bitbucket (which has had read only repo keys for a while) as repo keys are kind of a pain to use.