singer-io / singer-io/tap-github
Feature Request: Support domain specification
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 76
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
A Stitch user requested the ability to be able to specify an internal Github endpoint to pull data from, which was not functioning when populating the repository name field of the integration. eg, "github.singer.com" rather than simply singer-io, where entering singer was non-functional.
They received 401 errors during extraction without much logging surrounding those auth errors, and the extractions eventually ended with schema mismatch (due to no values being returned).
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 files or tests. Start by locating the integration's repository-name configuration and GitHub extraction entry point; reproduce the 401 behavior with an internal GitHub endpoint. Done means the endpoint can be specified and authentication failures are sufficiently visible instead of ending as a schema mismatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100