Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Feature Request: Support domain specification

Open
#23 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #77 by @udzura — closed without merging

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

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.

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).

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from singer-io/tap-github

All issues in singer-io/tap-github

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.