GitHub Community
Just a Question #190994
-
🏷️ Discussion TypeQuestion 💬 Feature/Topic AreaCode Search and Navigation BodyWhat’s the easiest way for a beginner to find and fix ‘good first issue’ bugs in open-source repos without getting overwhelmed? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Search GitHub for "good first issue" label via the issues tab filter in any repo (e.g., popular ones like freeCodeCamp or VS Code), or use github.com/explore to browse trending projects with that label. Pick unassigned issues matching your skills/interests, read the repo's CONTRIBUTING.md, fork/clone, fix in a branch, and submit a PR comment first to confirm it's still open. Start small to build confidence without overwhelm. |
Beta Was this translation helpful? Give feedback.
-
|
Search GitHub for "Good first issue" label via the issues tab filter in any repo (e.g., popular ones like freeCodeCamp or VS Code), or use github.com/explore to browse trending projects with that label. Pick unassigned issues matching your skills/interests, read the repo's CONTRIBUTING.md, fork/clone, fix in a branch, and submit a PR comment first to confirm it's still open. Start small to build confidence without overwhelm. |
Beta Was this translation helpful? Give feedback.
-
|
Is this not the same reply as NotDizzyButFizzy? |
Beta Was this translation helpful? Give feedback.
Search GitHub for "good first issue" label via the issues tab filter in any repo (e.g., popular ones like freeCodeCamp or VS Code), or use github.com/explore to browse trending projects with that label. Pick unassigned issues matching your skills/interests, read the repo's CONTRIBUTING.md, fork/clone, fix in a branch, and submit a PR comment first to confirm it's still open. Start small to build confidence without overwhelm.