MeltanoLabs / MeltanoLabs/tap-gitlab
Add additional fields to epics and issues
Open
Nobody has claimed this yet.
community-contributed mr
flow::review
kind::feature
urgency::default
valuestream::ecosystem
- Dominant language
- Python
- Stars
- 12
- Forks
- 29
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
In GitLab by @aaronsteers on Aug 9, 2021, 12:22
As described in !42
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 locating the GitLab API extraction code and reviewing the referenced !42 for the intended epic and issue fields. Confirm which fields are required and where extracted records are defined; the work is done when those fields are consistently returned and covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100