Support for GitLab Components
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
Frogbot seem to have some difficulties to work inside a GitLab Component. We use to have Frogbot configured in a GitLab Template, but these are going to be deprecated soon. Therefore the feature request.
Problem in particular it seem that the "inputs" are not parsed correctly, and this makes Frogbot to fail.
Please test and adapt Frogbot to work not only for Templates but also for GitLab Components, as this is going to become a new standard.
Contributor 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.
Research direction
Start by locating Frogbot's GitLab Template handling and the code that parses CI inputs. Add coverage for GitLab Components, focusing on correct input parsing, then verify that Frogbot can run successfully from a Component as well as a Template.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, go
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100