Skip to content
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.

Sign up for GitHub

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

Jump to bottom

How to publish to Job Summary? #270

Open
ranouf opened this issue Mar 12, 2024 · 4 comments · May be fixed by #283
Open

How to publish to Job Summary? #270

ranouf opened this issue Mar 12, 2024 · 4 comments · May be fixed by #283
Assignees
@irongut
Labels
enhancement New feature or request

Comments

@ranouf
Copy link

ranouf commented Mar 12, 2024 •
edited
Loading

Hi,

Here is the YML I use to test, create a report and display the report to Job Summary:

  # Test .NET project
   - name: Test .NET project
     run: dotnet test --no-build --settings tests.runsettings --results-directory ./coverage -- "RunConfiguration.DisableAppDomain=true"
     
   # Generate Summary Report
   - name: Code Coverage Summary Report
     uses: irongut/[email protected]
     with:
       filename: coverage/**/coverage.cobertura.xml
       badge: true
       format: 'markdown'
       output: 'both'

   - name: Write to Job Summary
     run: cat CodeCoverage/SummaryGithub.md >> $GITHUB_STEP_SUMMARY

But I have an issue:

Run cat CodeCoverage/SummaryGithub.md >> $GITHUB_STEP_SUMMARY
cat: CodeCoverage/SummaryGithub.md: No such file or directory
Error: Process completed with exit code 1.

How can I publish the report in Job Summary (not as a comment)?

Thanks
@ranouf ranouf added the enhancement New feature or request label Mar 12, 2024
@ranouf
Copy link
Author

ranouf commented Mar 12, 2024

The file used was not the correct one:

- name: Write to Job Summary
    run: cat **code-coverage-results.md** >> $GITHUB_STEP_SUMMARY

@hazzik hazzik linked a pull request Apr 12, 2024 that will close this issue
Open
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days.

@github-actions github-actions bot added stale and removed stale labels Jun 11, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days.

@github-actions github-actions bot added stale and removed stale labels Sep 10, 2024
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days.

@github-actions github-actions bot added stale and removed stale labels Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@irongut irongut

Labels
enhancement New feature or request
Projects
Enhancements
Status: To do
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Automatically publish GitHub step summary hazzik/CodeCoverageSummary
2 participants
@ranouf @irongut