---
title: "Comment by Conor Sheehan on \"Netlify continuous deployment\" | Hashnode"
description: "Nice article! Only thing I&#39;d add is that at step 4, you don&#39;t have to give read and write access to all your github repositories! I wrote a blog post my"
url: "https://hashnode.com/posts/netlify-continuous-deployment/6272862e272fe72a917cce78/comment/6272fdfd19a4772a6c29b276"
---

[Discussion](https://hashnode.com/posts/netlify-continuous-deployment/6272862e272fe72a917cce78)

Comment [Netlify continuous deployment](https://hashnode.com/posts/netlify-continuous-deployment/6272862e272fe72a917cce78)

[Conor Sheehan](https://hashnode.com/@ConorSheehan1)

[May 4, 2022](https://hashnode.com/posts/netlify-continuous-deployment/6272862e272fe72a917cce78/comment/6272fdfd19a4772a6c29b276)

Nice article! Only thing I'd add is that at step 4, you don't _have_ to give read and write access to all your github repositories! I wrote a blog post myself about how you can still have CD without giving away all your access [conorsheehan1.hashnode.dev/netlify-deployments-fr…](https://conorsheehan1.hashnode.dev/netlify-deployments-from-github-without-giving-write-access)

I'd say that's especially relevant now with the recent [breach at heroku](https://status.heroku.com/incidents/2413).

IMO it's always better to push your code to a hosting service, rather than giving them a broad scope of access and letting them pull it.

[victor josiah](https://hashnode.com/@Jovick-coder)

[May 5, 2022](https://hashnode.com/posts/netlify-continuous-deployment/6272862e272fe72a917cce78/comment/6272fdfd19a4772a6c29b276#reply-6273e57e5ac8834093048d15)

Thanks so much for the feedback, it is really helpful. Nice article [conorsheehan1.hashnode.dev/netlify-deployments-fr…](https://conorsheehan1.hashnode.dev/netlify-deployments-from-github-without-giving-write-access)
