---
title: "Conor Sheehan (@ConorSheehan1) | Hashnode"
description: "I'm software engineer from Dublin, Ireland"
url: "https://hashnode.com/@ConorSheehan1"
---

@ConorSheehan1

# Conor Sheehan

@ConorSheehan1 · Dublin, Ireland · Joined April 2022

[Website](https://linktr.ee/ConorSheehan1)

## Comments

[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 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. 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.](https://hashnode.com/posts/netlify-continuous-deployment/6272862e272fe72a917cce78/comment/6272fdfd19a4772a6c29b276)

Comment · Article · May 4, 2022 · [Netlify continuous deployment](https://hashnode.com/posts/netlify-continuous-deployment/6272862e272fe72a917cce78)

[Nice article! IMO it's worth noting most git platforms (github, bitbucket, etc.) support closing issues with specific commit keywords and an issue reference. E.g. fix infinite recursion bug, closes #111](https://hashnode.com/posts/commit-like-a-pro/626be9dab7dcabd258e74315/comment/626c4f51a2d355d4df43d20a)

Comment · Article · Apr 29, 2022 · [Commit Like a Pro](https://hashnode.com/posts/commit-like-a-pro/626be9dab7dcabd258e74315)
