MeltanoLabs / MeltanoLabs/tap-github
Get databaseId for organizations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20
- Forks
- 60
- Avg merge
- 20h 29m
- Merged PRs (30d)
- 6
Description
Following up on #112, we should:
- create a utility function to avoid duplication between repos and users streams
- use this util to implement a similar behavior for organizations and their children's streams
Some initial thoughts on refactoring
Technically, user{i} could be item{i} and we could extract the TempStream as a ContextStream to be shared between users, repos, and orgs streams
Some pseudo code of what I am thinking about:
ContextStream(request_records, request_body) -> [request_body_reponses]
repo:
request_records = [{repo, org}]
request_body = "{nameWithOwner, databaseId, id: nodeId }"
users
request_records = [{login}]
request_body = "{login, databaseId, id: nodeId }"
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 comparing the existing repos and users streams, then review the follow-up context from #112 and the proposed TempStream/ContextStream design. Done means organizations and their child streams expose databaseId and node id through shared logic without duplication between repos, users, and organizations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100