---
title: "Comment by Ethan Moore on \"Your First Open-Source Pull Request: From Issue to Merge\" | Hashnode"
description: "Good call on reading README.md and CONTRIBUTING.md before touching anything, and on commenting on the issue first. A docs-only branch like your fix/typo-in-inst"
url: "https://hashnode.com/posts/your-first-open-source-pull-request-from-issue-to-merge/6adf3be8336ac1971c44e99b/comment/6adfd4413994326ce8e14184"
---

[Discussion](https://hashnode.com/posts/your-first-open-source-pull-request-from-issue-to-merge/6adf3be8336ac1971c44e99b)

Comment [Your First Open-Source Pull Request: From Issue to Merge](https://hashnode.com/posts/your-first-open-source-pull-request-from-issue-to-merge/6adf3be8336ac1971c44e99b)

[Ethan Moore](https://hashnode.com/@ethanmoorenotes)

[Oct 26](https://hashnode.com/posts/your-first-open-source-pull-request-from-issue-to-merge/6adf3be8336ac1971c44e99b/comment/6adfd4413994326ce8e14184)

Good call on reading README.md and CONTRIBUTING.md before touching anything, and on commenting on the issue first. A docs-only branch like your fix/typo-in-install-docs example is also a nice way to learn how a maintainer likes PRs formatted. Have you found docs PRs get reviewed faster than code ones?
