l3montree-dev / l3montree-dev/devguard
Simplify the deep gitlab integration. There is no sense in providing an asset name. The gitlab ci does already know the project id - devguard knows it as well.
Open
Nobody has claimed this yet.
component/devguard-api
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
This issue has no description.
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
The issue names the deep GitLab integration but provides no files, tests, or entry points. Locate where the integration receives the asset name and where the GitLab CI project ID is available, then trace how DevGuard uses both values. Done means the integration no longer requires an asset name and consistently uses the project ID.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, go
- Domain
- ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100