ci(semver): restore sticky PR comment for version-increment check#573
Open
sandersaares wants to merge 4 commits into
Open
ci(semver): restore sticky PR comment for version-increment check#573sandersaares wants to merge 4 commits into
sandersaares wants to merge 4 commits into
Conversation
The semver-check job posted a fresh PR comment on every push, cluttering PRs with duplicates. Restore the marocchino/sticky-pull-request-comment action (header: semver-check) so the per-crate report is maintained as a single comment updated in place. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 69895436-a324-4370-b552-22d64a3369e4
Contributor
There was a problem hiding this comment.
Pull request overview
Restores “sticky” behavior for the semver version-increment report in CI so that PRs get a single updated comment instead of a new comment on every push, reducing PR timeline noise.
Changes:
- Update the semver job description to reflect sticky comment behavior.
- Replace
gh pr commentwithmarocchino/sticky-pull-request-commentkeyed by thesemver-checkheader.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The version-increment verdict stays informational (an under-increment never fails the build), but the check must actually execute: drop continue-on-error from the Semver Report step so an operational failure blocks and gets fixed rather than being silently skipped. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 69895436-a324-4370-b552-22d64a3369e4
ralfbiedert
approved these changes
Jul 14, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #573 +/- ##
=======================================
Coverage 100.0% 100.0%
=======================================
Files 360 360
Lines 27886 27886
=======================================
Hits 27886 27886 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Comment on lines
264
to
+268
| if: steps.report.outputs.publishing == 'true' && github.event.pull_request.head.repo.full_name == github.repository | ||
| env: | ||
| GH_TOKEN: ${{ github.token }} | ||
| run: gh pr comment ${{ github.event.pull_request.number }} --body-file semver-comment.md | ||
| uses: marocchino/sticky-pull-request-comment@468942ec889968f45256a969e13c75bc7cdec2b6 # v3.0.4 | ||
| with: | ||
| header: semver-check | ||
| path: semver-comment.md |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The semver version-increment check posted a fresh PR comment on every push, cluttering PRs with duplicate comments (e.g. #570).
This restores the
marocchino/sticky-pull-request-commentaction (keyed by thesemver-checkheader) that the job used previously, so the per-crate report is maintained as a single sticky comment that is updated in place on each push instead of a new comment every time.