Skip to content
Discussion options

You must be logged in to vote

The easiest way in my opinion is to start with something you already use every day — your daily drivers (apps, programs, tools, websites, etc.).

If you’re already familiar with it, you know what it does, what’s missing, and what could be better. Reading the code becomes easier too, because you’ve seen the thing in action.

Here’s a simple path to follow:

  1. Pick a project you actually use – it could be a text editor, browser extension, command‑line tool, or even a game.
  2. Use it and take notes – every bug, missing feature, or small annoyance is a possible contribution.
  3. Check the repo’s contributing guide (CONTRIBUTING.md), so you know how the maintainers want things done.
  4. Start with small fixes

Replies: 3 comments 2 replies

Comment options

You must be logged in to vote
1 reply
@ankit1350
Comment options

Answer selected by ankit1350
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@ankit1350
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Question Ask and answer questions about GitHub features and usage Programming Help Discussions around programming languages, open source and software development
3 participants