-
Notifications
You must be signed in to change notification settings - Fork 2.4k
ci: publish fork-PR test reports via workflow_run #4643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+59
−17
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,36 @@ | ||
| name: Test Report | ||
|
|
||
| # Publishes test results for runs of the CI workflow, including pull requests | ||
| # from forks. The CI workflow itself runs with a read-only token (GitHub forces | ||
| # this for fork PRs) and only uploads the .trx files as artifacts. This workflow | ||
| # is triggered by workflow_run, so it runs in the *base repository* context with | ||
| # a writable token and can call the Checks API to publish inline reports. | ||
| # See issue #4642. | ||
|
|
||
| on: | ||
| workflow_run: | ||
| workflows: [CI] | ||
| types: | ||
| - completed | ||
|
|
||
| permissions: | ||
| contents: read | ||
| actions: read | ||
| checks: write | ||
|
|
||
| jobs: | ||
| report: | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - name: Publish Test Results | ||
| uses: dorny/test-reporter@v1 | ||
| with: | ||
| # Download every test-results-* artifact from the triggering CI run and | ||
| # publish one check per platform, e.g. "Test Results (Linux)". | ||
| artifact: /test-results-(.*)/ | ||
| name: Test Results ($1) | ||
| path: '**/*.trx' | ||
| reporter: dotnet-trx | ||
| # A build that fails before producing any .trx shouldn't make this | ||
| # report red; the CI run already reflects that failure. | ||
| fail-on-empty: 'false' |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed by scoping
id-token: writeto thebuild-windowsjob only (the workflow default is nowcontents: read), so the Linux build job and any future job carry no OIDC. I kept signing/publishing inbuild-windowsrather than splitting into a dedicated job because that path only runs onmainand is untested-by-CI; restructuring it risks silently breaking releases for a marginal gain. Worth noting the fork escalation specifically isn't reachable: GitHub forces the token read-only for forkpull_requestruns and will not honorid-token: write, so forks cannot mint an OIDC token here at all. The residual surface is trusted same-repo collaborators, and the Azure federated credential should be subject-constrained on the Azure side regardless. (commit 8c86567)