ci: use PR number from github context for coverage report#6
Open
knecasov wants to merge 1 commit into
Open
Conversation
|
|
knecasov
force-pushed
the
fix-coverage-pr-lookup
branch
2 times, most recently
from
March 10, 2026 18:45
4554fff to
cf20c51
Compare
- split PR comment into separate workflow_run-triggered workflow so the token has write permissions for fork PRs - pass PR number and coverage report via artifact between workflows Signed-off-by: Klara Necasova <knecasov@redhat.com>
knecasov
force-pushed
the
fix-coverage-pr-lookup
branch
from
March 11, 2026 08:57
cf20c51 to
e05ab03
Compare
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.
What
Replace the API-based PR lookup with
github.event.pull_request.numberfor posting the coverage report comment to a PR.Why
The previous approach used
github.repository_ownerto find the PR, which does not work for PRs from forks where the branch owner differs from the upstream repository owner.