Readme needs to be updated to include releases
A pull request for this has already been merged.
- #148 by @loeakaodas — merged
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 58/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- github, python
- Domain
- documentation
Research direction
Start by opening the repository README and the linked GitHub releases API documentation. Update the README to include releases information, then verify that the added link and wording clearly direct readers to repository releases.
Written by the indexing model from the issue text.
Description
- Dominant language
- Python
- Stars
- 76
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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 singer-io/tap-github
-
Stitch - Projects (classic) has been deprecated in favor of the new Projects experiencePossibly taken @skuttleman claimed this 18 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 38/100
singer-io/tap-github#215 · 2 assignees ·
-
Re-add `files` and `stats` to `PrCommits` streamMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
singer-io/tap-github#202 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
singer-io/tap-github#194 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
singer-io/tap-github#186 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
singer-io/tap-github#185 ·
All issues in singer-io/tap-github
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aicell-lab/bioengine#232 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
modelscope/evalscope#1836 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
jbaruch/speaker-toolkit#480 ·
Maintainers usually reply within 1 day