MeltanoLabs / MeltanoLabs/tap-gitlab
Extract issues and associated entities for entities outside of the fetched group that belong to an Epic
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 29
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
In GitLab by @iroussos on Jun 14, 2019, 07:21
Currently, we fetch all projects, issues, etc for the specified group when tap-gitlab runs.
With the introduction of Epics, there is a possibility that some issues in an epic reside in a project outside of the group extracted.
An example can be seen by one of the epics in the Meltano Group.
The project some of the issues reside was moved out of the Meltano Group resulting in those issues being referenced by the Epic, but not fetched by tap-gitlab as they are not part of the Group fetched.
We should recursively identify such issues and fetch them and their relevant entities when Epics are extracted.
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 tracing tap-gitlab's group and Epic extraction entry points and the GitLab API calls they use. Follow how Epic-linked issues are represented, then determine how recursively fetched issues and their associated entities should enter the extraction. Done means issues outside the selected group, such as those linked from an Epic, and their relevant entities are extracted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, 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