Link to fork count does not point to members
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Search the repository for the fork-count button and inspect how its current GitHub Network URL is assembled. Change the destination from /network to /network/members, then verify the rendered fork-count link points to the members page.
Written by the indexing model from the issue text.
Description
Presently, if we click on fork count, it points to github.com/user/repo/network. But to see who all have forked the repo, it should point to github.com/user/repo/network/members instead.
- Dominant language
- JavaScript
- Stars
- 2.9k
- Forks
- 263
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mdo/github-buttons
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mdo/github-buttons#219 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mdo/github-buttons#156 · 3 comments ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mdo/github-buttons#151 ·
-
Add queries checksOpen
Difficulty 3/5 1-2 days Newbie friendliness 42/100
mdo/github-buttons#142 ·
-
Add faviconsOpendocs
Difficulty 3/5 1-2 days Newbie friendliness 25/100
mdo/github-buttons#139 ·
All issues in mdo/github-buttons
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
keyxmakerx/Chronicle#967 ·
Maintainers usually reply within 1 day
-
good first issue hacktoberfest
Difficulty 1/5 Under an hour Newbie friendliness 92/100
RogueAlg0/taken#386 · 3 comments ·
Maintainers usually reply within 1 day
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
LearningCircuit/local-deep-research#7067 ·
Maintainers usually reply within 1 day