How to detect when issues move repos
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
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.
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?
- 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
- 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.
More from singer-io/tap-github
-
Stitch - Projects (classic) has been deprecated in favor of the new Projects experiencePossibly taken @skuttleman claimed this 16 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 38/100
singer-io/tap-github#215 · 2 assignees ·
-
Re-add `files` and `stats` to `PrCommits` streamMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
singer-io/tap-github#202 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
singer-io/tap-github#194 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
singer-io/tap-github#186 · 1 comment · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
singer-io/tap-github#185 ·
All issues in singer-io/tap-github
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
pytest-dev/pluggy#757 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
NousResearch/hermes-agent#134960 ·
Maintainers usually reply within 1 day
-
HTML backend: `<br>` leaks the internal sentinel U+E000 into list items, headings and captionsPossibly taken @morten-lagabote claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
docling-project/docling#4671 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
good first issue hacktoberfest infra
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day