content: Launch post — Replay Recent GitLab and Bitbucket History at Trigger Setup - #836
content: Launch post — Replay Recent GitLab and Bitbucket History at Trigger Setup#836frances720 wants to merge 1 commit into
Conversation
…Trigger Setup Generated by launch-post skill.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
There was a problem hiding this comment.
Inbound docs PR review — GitLab/Bitbucket replay launch post
Reviewed as a documentation-content PR (one new blog post under src/content/blog/product-updates/, human author). I verified every factual claim against the backing source (Promptless/promptless#3497, merged 2026-06-04) and the live docs for all three providers, and checked doc quality, audience fit, and repo conventions.
What's correct (verified against source):
- 30-day replay window for GitLab MRs and Bitbucket PRs — ✅ matches source (
replay_preview.py30-day cutoff; provider coverage flipped from GitHub-only to github/gitlab/bitbucket in #3497). - GitHub-parity framing — ✅ GitHub was the only provider before this change.
- "The onboarding preview shows… counts and recent items, grouped by provider" — ✅ matches the per-provider preview grouping added in #3497, and is documented in
github-prs.mdx. - "The replay runs once at setup. After that, the trigger processes new activity as usual." — ✅ bootstrap marks the pipeline complete after the one-time run; ongoing webhook processing is unchanged.
- "enable the replay option in the trigger creation flow… No separate configuration is required" — ✅ consistent with the published docs, which describe an enable-able "Replay recent MRs/PRs" option.
- Both doc links resolve to the correct current slugs (
/docs/connect/triggers/gitlab-merge-requests,/docs/reference/integrations/bitbucket). Terminology ("merge request", "pull request"), frontmatter, CTA imports, and Title-Case blog-post title all follow this collection's conventions.
One thing to address (see inline): the "within an hour of setup" timing claim in The problem is a specific performance figure that isn't backed by the source or the docs (replay runs asynchronously in the background with a progress indicator; there's no stated time bound). Suggest softening it so the post doesn't set an expectation the product doesn't guarantee.
Merge decision stays with you — this is a documentation-specialist check, not a gate.
|
|
||
| ## The problem | ||
|
|
||
| When GitHub PR triggers added replay support, teams onboarding to Promptless could generate an initial batch of documentation suggestions from recent work, not just from future activity. That made a big difference for pilots and evaluations: you'd see real suggestions for real code within an hour of setup, rather than waiting for the next PR to merge. |
There was a problem hiding this comment.
Correctness-against-source: "you'd see real suggestions for real code within an hour of setup" is a specific timing claim that neither the backing PR (Promptless/promptless#3497) nor the docs support. Replay runs asynchronously in the background (the provider trigger docs describe a "Processing last 30 days…" spinner, with no stated completion time), and processing time scales with how many MRs/PRs are in the window — so "within an hour" could over-promise for a busy repo.
Suggest dropping the specific figure, e.g.:
That made a big difference for pilots and evaluations: you'd see real suggestions for real code shortly after setup, rather than waiting for the next PR to merge.
(Everything else in the post checks out against source.)
2 participants
Feature
When creating a new GitLab MR or Bitbucket PR trigger, you can now enable "Replay recent MRs/PRs" to process the last 30 days of merge requests and pull requests — bringing GitLab and Bitbucket to parity with GitHub's existing replay onboarding option.
Entries considered this run
Window: 2026-08-03 → 2026-08-10.
20 commits in window. 20 entries considered, 2 qualified (this PR covers 1; self-serve Teams connect in a separate PR).
Covered entry (full text)
Source: commit bfa7994 (June 2026 changelog entry).
PR(s) researched
File
src/content/blog/product-updates/gitlab-bitbucket-pr-replay.mdxAI-generated draft — needs human review before publishing.
Generated by Claude Code