ci: Fix semver PR comment check for fork PRs #205
+2
−2
Conversation
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
Fork PRs have read-only GITHUB_TOKEN and cannot post comments. Skip the sticky-pull-request-comment steps when the PR comes from a fork to avoid "Resource not accessible by integration" errors. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #205 +/- ##
=======================================
Coverage 100.0% 100.0%
=======================================
Files 106 106
Lines 6845 6845
=======================================
Hits 6845 6845 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
schgoo
changed the title
Member
|
So PRs from a fork won't get notified about semver breaks? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fork PRs have read-only GITHUB_TOKEN and cannot post comments. Trying to see if we can skip the sticky-pull-request-comment steps when the PR comes from a fork to avoid "Resource not accessible by integration" errors.