singer-io / singer-io/tap-github
How to detect when issues move repos
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 76
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
When I move an issue from one repo to another, it looks like there's no way to tell that the issue is no longer part of the first repo. So, when I query on this, the issue appears in both repos.
Any ideas how to handle this? Is this something I can handle in my queries, or would the tap need to be modified?
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 how the GitHub API represents issues moved between repositories and how the tap currently queries issue records. Determine whether the existing query data can distinguish moved issues; done means issues moved out of the original repository no longer appear there, or the required tap change is clearly identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100