Skip to main content
All posts
Open Source6 min read10 views

How to Make Your First Open Source Contribution

A step-by-step guide for beginners: choose a project, find a good first issue, fork the repository, make a change and open your first pull request.

Admin

FOSS Andhra community volunteer writing about free and open source software, education and developer tools from Andhra Pradesh.

Making your first open source contribution can feel intimidating, but it is a learnable process, and not every contribution is code. This guide shows you how to go from "I want to contribute" to an accepted pull request.

Contributions are more than code

Projects need many kinds of help. You can:

  • Fix typos and improve documentation
  • Translate the software or its docs into Telugu or other languages
  • Report and reproduce bugs
  • Test new releases
  • Improve design and accessibility
  • Answer questions from other users

Documentation fixes are a very common first contribution.

Step 1: Choose a project you actually use

Pick software you already use or care about. You will understand the problem better and stay motivated. Check that the project is active: recent commits, open issues being answered, and a welcoming tone.

Step 2: Read the contributor guides

Look in the repository for these files:

  • README: what the project does and how to run it
  • CONTRIBUTING: how the maintainers want contributions made
  • CODE_OF_CONDUCT: the community's rules of behaviour

Following these saves everyone's time.

Step 3: Find a beginner-friendly issue

Search the issue tracker for labels such as good first issue, help wanted or beginner. Read the issue carefully. If you want to work on it, leave a short comment saying so, to avoid duplicate effort.

Step 4: Fork, clone and branch

On GitHub, fork the repository to copy it to your account, then work locally:

git clone https://github.com/YOUR-USERNAME/project-name.git
cd project-name
git checkout -b fix-typo-in-readme

Creating a branch keeps your change separate from the main code.

Step 5: Make the change and test it

Keep your change small and focused on the issue. If the project has tests, run them. Follow the existing code style and naming.

Step 6: Commit and push

git add .
git commit -m "Fix typo in README installation section"
git push origin fix-typo-in-readme

Write a clear commit message that explains what you changed.

Step 7: Open a pull request

On GitHub, click Compare & pull request. Explain what you changed and why, and link the issue (for example, "Fixes #123"). Be patient: maintainers are often volunteers.

Step 8: Respond to feedback

Reviewers may ask for changes. That is normal and part of learning. Reply politely, update your branch, and push again; the pull request updates automatically.

Tips for beginners

  • Start small. A merged one-line fix beats an abandoned large change.
  • Ask questions in the project's chat or discussion forum.
  • Do not take review comments personally.
  • Keep a record of your contributions on your GitHub profile; it becomes your portfolio.

Where to get help

Our community can help you take the first step. Join FOSStar, come to one of our events, and look at the internship openings where you can work on real open source projects.

New to the topic? Read What Is Open Source Software? first.

Take the next step

Explore our internship openings, become a FOSStar member, or meet the community at an upcoming event.