singer-io / singer-io/tap-github
Add missing fields to streams
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 76
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
Following fields are missing from the streams:
- Pull Requests
[ '_links', 'assignee', 'assignees', 'author_association', 'base', 'comments_url', 'commits_url', 'diff_url', 'head', 'html_url', 'issue_url', 'labels', 'locked', 'merge_commit_sha', 'milestone', 'patch_url', 'requested_reviewers', 'requested_teams', 'review_comment_url', 'review_comments_url', 'statuses_url', ] - Reviews
['_links', 'author_association', 'submitted_at', 'user.avatar_url', 'user.events_url', 'user.followers_url', 'user.following_url', 'user.gists_url',
'user.gravatar_id', 'user.html_url', 'user.organizations_url', 'user.received_events_url', 'user.repos_url', 'user.site_admin', 'user.starred_url', 'user.subscriptions_url', 'user.type', 'user.url'] - Stargazers
['user.avatar_url', 'user.events_url', 'user.followers_url', 'user.following_url', 'user.gists_url', 'user.gravatar_id', 'user.html_url', 'user.login', 'user.organizations_url', 'user.received_events_url', 'user.repos_url', 'user.site_admin', 'user.starred_url', 'user.subscriptions_url', 'user.type', 'user.url'] - Collaborators
['avatar_url', 'events_url', 'followers_url', 'following_url', 'gists_url', 'gravatar_id', 'html_url', 'organizations_url', 'permissions', 'received_events_url', 'repos_url', 'site_admin', 'starred_url', 'subscriptions_url'] - Assignees
['avatar_url', 'events_url', 'followers_url', 'following_url', 'gists_url', 'gravatar_id', 'html_url', 'organizations_url', 'received_events_url', 'repos_url', 'site_admin', 'starred_url', 'subscriptions_url'] - Commits
['author', 'commit.verification', 'committer'] - Issues
['assignee', 'assignees', 'author_association', 'body', 'closed_at', 'comments', 'comments_url', 'created_at', 'events_url', 'html_url', 'labels', 'labels_url', 'locked', 'milestone', 'number', 'repository_url', 'state', 'title', 'url', 'user']
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
The issue does not name any files, tests, or entry points. Start by locating the stream definitions for Pull Requests, Reviews, Stargazers, Collaborators, Assignees, Commits, and Issues, then compare their output with the listed fields. Done means each stream exposes the requested fields and relevant tests confirm them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100