5 ms·
There's an issue for this in GitLab's tracker: https://gitlab.com/gitlab-org/gitlab/-/issues/14259 https://gitlab.com/gitlab-org/gitlab/-/issues/14259 Sadly,
by antsar 6y ago
There's an issue for this in GitLab's tracker:
https://gitlab.com/gitlab-org/gitlab/-/issues/14259 https://gitlab.com/gitlab-org/gitlab/-/issues/14259
Sadly, it's four years old and seems pretty stagnant.
- samanthalee233 6y agoHey there, I'm a GitLab community advocate, just wanted to thank you for brining attention to this issue, our team commented to get the conversation moving today: https://gitlab.com/gitlab-org/gitlab/-/issues/14259#note_327134034 https://gitlab.com/gitlab-org/gitlab/-/issues/14259#note_327...
- gravypod 6y agoIt's unfortunate gitlab is built as a monolith. I'd be very capable of writing the code for implementing such a feature myself if gitlab had a first class API. The code, as we all know, would look something like this: for commit diff = commit.diff for line in diff.result if 'todo' in line line_id = hash(line) if existing := issues.find(tags={'todo_id': line_id}): existing.update(code_url = new line location) else: issues.create(....) But because these APIs aren't first class a change like this requires deep knowledge of gitlab's internals and acceptance and prioritization of features from gitlab's core team.