[Bug]: system comments are hidden from GitLab MRs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/server
Steps to reproduce
- Open GitLab MR
- Have someone approve MR
- Nothing is shown in t3code
Expected behavior
Ideally t3 would show approval status so we can easily see which MRs are approved but since that seems like a much larger feature, I'd like to have system-level notes exposed in at least the timeline but better also in the comments view as well. This will show assignment changes, pushes, approvals, rejections, etc.
Actual behavior
The timeline is synthetic and doesn't show all of the things that GitLab shows. The comments section shows no comments. This is a deal breaker because I have no idea in t3 if the MR is approved and if I should attempt to merge it which means I need to open all of my MRs in the browser.
Impact
Major degradation or frequent failure
Version or commit
0.0.39-nightly.20260904.1280
Environment
Windows + Remote SSH running Linux
Logs or stack traces
Screenshots, recordings, or supporting files
No response
Workaround
No response
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 in apps/server and trace how GitLab merge request timelines and comments are fetched and filtered. Reproduce the approval scenario, then verify that system-level notes such as approvals, pushes, assignments, and rejections appear in the timeline or comments view alongside regular comments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100