---
title: "Discussion on \"Your First Open-Source Pull Request: From Issue to Merge\" | Hashnode"
description: "Discussion on \"Your First Open-Source Pull Request: From Issue to Merge\". Contributing to open source sounds intimidating the first time. Big codebases, strangers reviewing your code, Git commands you only half remember. The good news: the process is the same almost everywh"
url: "https://hashnode.com/posts/your-first-open-source-pull-request-from-issue-to-merge/6adf3be8336ac1971c44e99b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Your First Open-Source Pull Request: From Issue to Merge](https://nexen.hashnode.dev/your-first-open-source-pull-request-from-issue-to-merge?utm_source=hashnode&utm_medium=feed)

Contributing to open source sounds intimidating the first time. Big codebases, strangers reviewing your code, Git commands you only half remember. The good news: the process is the same almost everywh

Oct 26 · 4 min read · nexen.hashnode.dev  
Read the article

-   [#opensource](https://hashnode.com/tag/opensource)
-   [#github](https://hashnode.com/tag/github)
-   [#git](https://hashnode.com/tag/git)
-   [#beginners-guide](https://hashnode.com/tag/beginners-guide)

## Written by

[Vinay Thangellapally](https://hashnode.com/@Vinay1213)

@Vinay1213 · Hyderabad, India

  
[View profile](https://hashnode.com/@Vinay1213)

Research Analyst | SAP CPI Developer | Automation & Android Builder

Research Analyst with a physics and mathematics background. I build automation tools with Python and Google Apps Script, freelance on SAP Cloud Platform Integration (CPI), and develop Android apps with Jetpack Compose. Previously ML Data Associate at Amazon (Alexa ASR/NLU). I write about SAP CPI, automation, open source, and the things I build.

## Responses 1

Markdown supported · ⌘↵ to post

[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?
