Repository navigation
Moved the publishing of test results to a separate workflow - #67
Open
xperiandri wants to merge 1 commit into
Open
xperiandri wants to merge 1 commit into
xperiandri wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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.
Summary
No dependencies, one commit. The step
Publish Test Resultsfails on the Windows image becauseEnricoMi/publish-unit-test-result-actionfinds no Python interpreter there. This pull request publishes the results from a second workflow onubuntu-latest, as FAKE and FSharp.Data.GraphQL do.Changes, things to know, verification
Changes
build.yamlno longer publishes. It uploads the.trxfiles as the artifacttest-results-<OS>and the event file as the artifactEventFile(bothif: !cancelled(), so a failed test run is still published).publish-test-results.yml, started byworkflow_runafterBuild: it downloads both artifacts, runsEnricoMi/publish-unit-test-result-action@v2(comment on the pull request, check,comment_mode: always) and then does the badge steps that were inbuild.yaml(they read the output of the action, so they had to move with it). The badge goes to the Gist only for a push tomain, as before.Good to know
workflow_runworkflow runs only from the default branch, so the comment appears for the first time on pull requests after this one is merged.GIST_TOKENis read in the new workflow now..slnxformat #53-Build withdotnet build#58) change other lines of the build workflow; the conflicts, if any, are small.Not verified
The YAML was checked by reading only. The new workflow could not run end to end: it needs the file on the default branch. The upload steps and the badge steps are the old ones, moved.
🤖 Generated with Claude Code