l3montree-dev / l3montree-dev/devguard
Creation of GitLab issues from DevGuard dependency risks is broken
Open
Nobody has claimed this yet.
bug
component/devguard-api
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
Describe the bug
DevGuard is unable to create issues in GitLab if manually requested by the user.
Using the "Reporting range" feature DevGuard creates issues as expected
https://github.com/user-attachments/assets/2414e9eb-a403-4f57-9f36-9c18ebdc5df7
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
Reproduce the failure by manually requesting creation of a GitLab issue from a DevGuard dependency risk, then compare it with the working Reporting range flow. Trace both issue-creation paths and verify that manual requests create the expected GitLab issue without breaking the existing Reporting range behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, go
- Domain
- api, backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100