| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
The PR bump preview workflow passed �ody-includes to peter-evans/create-or-update-comment@v5, but that action has no such input -- it only creates a new comment, or updates one passed via comment-id. Every run therefore appended another duplicate comment (e.g. 6 stacked on #2007). Insert a peter-evans/find-comment@v3 step ahead of the post step to look up an existing preview comment by sentinel marker and bot author, then pass its id (empty for the first run) to create-or-update-comment. This matches the documented pattern in the action's README and keeps the bump preview as a single sticky comment per PR. Apply the same fix to the docs/tutorials/github_actions.md example so other projects copying the workflow don't inherit the bug, and also bump the example from create-or-update-comment@v4 to @v5 to match the workflow. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
🔍 Commitizen bump previewMerging this PR will produce the following bump: bump: version 4.16.2 → 4.16.3 tag to create: v4.16.3 increment detected: PATCH |
Sorry, something went wrong.
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## master #2008 +/- ##
=======================================
Coverage 98.24% 98.24%
=======================================
Files 61 61
Lines 2785 2785
=======================================
Hits 2736 2736
Misses 49 49 ☔ View full report in Codecov by Harness. |
Sorry, something went wrong.
There was a problem hiding this comment.
Updates the PR bump preview workflow to update a single existing “Commitizen bump preview” comment instead of posting a new one on every run, aligning the workflow and the tutorial documentation with the supported peter-evans/create-or-update-comment usage pattern.
Changes:
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| docs/tutorials/github_actions.md | Updates the documented workflow snippet and explanation to use find-comment + comment-id with create-or-update-comment@v5. |
| .github/workflows/pr-bump-preview.yml | Makes the bump preview comment “sticky” by finding an existing comment and updating it in place via comment-id. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
Description
The PR bump preview workflow appends a new comment on every run instead of editing the previous one -- see #2007, which has 6 duplicate comments.
Cause: it passes body-includes to peter-evans/create-or-update-comment@v5, but that action has no such input (see its action.yml). It only creates new comments, or updates one identified by comment-id.
Fix: insert a peter-evans/find-comment@v3 step ahead of the post step, then pass its comment-id output (empty on first run) to create-or-update-comment. Matches the documented pattern in the action's README. The same fix is applied to the tutorial example in docs/tutorials/github_actions.md (also bumped @v4 -> @v5 to match the workflow).
Checklist
Was generative AI tooling used to co-author this PR?
Generated-by: GitHub Copilot CLI following the guidelines
Code Changes
Documentation Changes
Expected Behavior
After merge, each PR has at most one Commitizen bump preview comment from github-actions[bot], updated in place on subsequent runs. Pre-existing duplicate comments are not pruned by this PR.
Steps to Test This Pull Request
After merge:
Additional Context
Related: #1957 (workflow originally added).