Skip to content

content: Launch post — Suggestion Citations Now Post Inline on GitLab Merge Requests - #869

Open
frances720 wants to merge 2 commits into
mainfrom
articles/2026-08-17-gitlab-inline-citation-comments
Open

content: Launch post — Suggestion Citations Now Post Inline on GitLab Merge Requests#869
frances720 wants to merge 2 commits into
mainfrom
articles/2026-08-17-gitlab-inline-citation-comments

Conversation

@frances720

Copy link
Copy Markdown
Contributor

Feature

When Promptless opens or updates a merge request on GitLab, suggestion citations now post as diff-positioned discussion threads directly on the MR, bringing GitLab to parity with the existing GitHub behavior.

Entries considered this run

Window: 2026-08-10 → 2026-08-17 (7 days). 5 commits, 5 entries considered, 2 qualified.

# Entry Decision Reason
1 GitLab MR comment 👀 acknowledgment — Adds a 👀 reaction to GitLab MR comment mentions (commit a30968d, PR #4501) SKIP Minor acknowledgment polish; doesn't unlock a new workflow
2 Run documentation checks on a schedule — New schedule trigger type: run standing instructions on a repeating cron schedule (commit def75a3, PR #4505) QUALIFIES New trigger type that enables proactive, event-free documentation audits — a genuinely new class of workflows
3 CI failures as a distinct "CI failed" event — CI failures now show as their own event in the suggestion timeline, separate from human feedback items (commit d692a8f) SKIP UI clarity improvement; doesn't unlock a new use case
4 GitLab inline citation comments — Citations post as diff-positioned discussion threads on GitLab MRs (commit eca7d1f, PR #4514) QUALIFIES Meaningful new UX for GitLab users: reviewers can see citation context in GitLab without switching to the dashboard
5 Research breakdown KB inline + delegated research attribution — Research breakdown shows KB reads in sequence and labels delegated subagent research (commit 730cb63, PR #4528) SKIP Display polish to an existing panel; doesn't unlock a new workflow

Covered entry (full text)

Post citations as inline comments on GitLab merge requests: Citations for a suggestion now post as diff-positioned discussion threads directly on the GitLab merge request, bringing GitLab to parity with the existing GitHub behavior, with an unanchored file-and-line thread as a fallback when a citation can't be anchored to the diff. See GitLab projects.

Source: commit eca7d1f.

PR(s) researched

File

src/content/blog/product-updates/gitlab-inline-citation-comments.mdx

AI-generated draft — needs human review before publishing.


Generated by Claude Code

… Merge Requests

Generated by launch-post skill.
@vercel

vercel Bot commented Aug 17, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
promptless-docs Ready Ready Preview Aug 17, 2026 4:19pm

Request Review

@promptless promptless Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Documentation review (Promptless docs specialist pass). Thanks for the post, Frances — the structure, frontmatter, house template (problem / what it does now / who benefits / how to use it), CTA placement, and both internal links all check out, and I verified the core mechanics against the source PR (Promptless/promptless#4514):

  • Citations posting as diff-positioned discussion threads on open and update — confirmed.
  • The unanchored file-and-line fallback when a citation can't be anchored to the diff — confirmed.
  • Threads appearing in the GitLab discussion panel alongside human review comments — confirmed.
  • Parity with GitHub, and the dashboard viewer still showing citations (MR comments are additive) — confirmed.

One correctness issue against source needs a fix before this is accurate to ship, plus one style nit — both in the How to use it paragraph (line 45). Details inline. Everything else is clean; this is a COMMENT (not a block) so you can address the gating claim and re-request.


## How to use it

Nothing to configure. Promptless posts citations on GitLab MRs automatically as long as `auto_create_pr` is enabled in your [publishing policies](/docs/reference/configuration-reference#policies). If you're already using Promptless with GitLab doc collections, citations will appear on new MRs going forward.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correctness (verified against source PR #4514) — please fix before publish. auto_create_pr is not the gate for citation posting, so "as long as auto_create_pr is enabled" is inaccurate and could mislead readers.

In the source, citation delivery is gated on the docs MR existing with its URL recorded (plus a resolved SHA and a GitLab/GitHub collection) — not on any policy flag. auto_create_pr only controls whether Promptless opens the MR automatically. A team that runs with auto_create_pr off but opens MRs another way (the dashboard "Create PR" button, Slack, or an explicit request) still gets inline citations — the current wording tells them the opposite.

Separately, same sentence: "citations will appear" uses future-tense "will" for product behavior, which the client style guide asks us to avoid — use present tense.

Suggested rewrite that fixes both:

Nothing to configure. Whenever Promptless opens or updates a docs merge request — however that MR was created — it posts the suggestion's citations on the MR. If you're already using Promptless with GitLab doc collections, citations appear on new MRs going forward.

(That rewrite drops the auto_create_pr/publishing-policies reference since it isn't the gate. If you'd like to keep a pointer to how MRs get created, the GitLab projects link you already cite at the end covers it.)

Citations post on any GitLab MR Promptless opens or updates, regardless
of how the MR was created — not gated on auto_create_pr. Also switches
"will appear" to "appear" per style guide (present tense for product
behavior).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants