Skip to content

fix: Fix typo: "responsivness" → "responsiveness" in finding-good-first-issue #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tcuong53-cell wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: Fix typo: "responsivness" → "responsiveness" in finding-good-first-issue #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions guides/finding-good-first-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,8 +61,6 @@ If the repo has no `CONTRIBUTING.md`, no PR template, and no obvious signs anyon

### Maintainer responsivness

<!-- TODO: contribution welcome — expand on what good vs slow maintainer response patterns look like -->

A rough heuristic: look at the last 5 closed PRs. How long between PR open and first maintainer comment? Under a week is great. Over a month means you're going to be waiting.

## A safer search workflow
Expand All @@ -83,4 +81,4 @@ Some sites pre-filter for beginner-friendliness:
- [up-for-grabs.net](https://up-for-grabs.net/)
- [firsttimersonly.com](https://firsttimersonly.com/)

These lists are useful but not magic — apply the same red-flag checks above before committing time to an issue.
These lists are useful but not magic — apply the same red-flag checks above before committing time to an issue.