look up real names of github accounts
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github, javascript
Research direction
The issue names no files, tests, or entry points. Inspect the repository's JavaScript entry point and the existing shoutout-generation flow first, then determine how GitHub profile data is obtained and verify that provided real names are used while missing names fall back to usernames.
Written by the indexing model from the issue text.
Description
Currently I open all github profile pages manually to see if the user provided their real username and use that in the shoutouts. If no name is provided, fallback to username
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 0
- 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 finnp/github-shoutouts
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Very first PROpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in finnp/github-shoutouts
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
swc-project/swc#12516 ·
Maintainers usually reply within 1 day
-
feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
omegaup/omegaup#10323 · 1 comment ·
Maintainers usually reply within 5 days
-
area/frontend good first issue kind/cooldown
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kestra-io/kestra#20702 · 1 comment ·
Maintainers usually reply within 1 day
-
Form-data fields are not parsed when importing a cURL requestPossibly taken @aayushbaluni claimed this today. Openbug status-new
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
bug MVP
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
saayam-for-all/webapp#1911 ·
Maintainers usually reply within 1 day