MeltanoLabs / MeltanoLabs/tap-github
Add stream `issue_reactions` (currently blocked)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20
- Forks
- 60
- Avg merge
- 20h 29m
- Merged PRs (30d)
- 6
Description
The goal here would be to gather information on who added an emote to which specific issue comments, and when.
As of now this probably isn't viable without using GraphQL. Logging for tracking purposes, but my expectation is that we won't deliver any time soon due to the logistic/performance challenges in dealing with this API.
The REST API would require pinging every issue and issue comment looking for the latest reaction data, and it's not clear if the issue or issue comment would even have their "last updated date" reset when new emotes/reactions are added.
Reactions API for the issue: docs.github.com/en/rest/reactions#list-reactions-for-an-issue
Reactions API for the issue comments: docs.github.com/en/rest/reactions#list-reactions-for-an-issue-comment
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing the linked GitHub REST endpoints for issue and issue-comment reactions, then investigate whether GraphQL can provide the required data efficiently. Done would mean a viable extraction approach for who reacted to each comment and when, but the issue currently records this as blocked by API and performance constraints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- api, data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100