-
Notifications
You must be signed in to change notification settings - Fork 27
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
feat: add output to step summary #21
Conversation
Thanks for fixing this critical bug of this otherwise great action! Used both options and they worked as expected. |
Can we merge please? We could use this |
You can use it in your workflow already like this: |
Checked this out. Works well: It's also worth noting unlike with separate reports, updating the workflow summary doesn't need write access to the repo, and thus will also work if you open a PR from a fork, like here. |
Great improvement @jcdickinson! |
- NOTE: the report step will not always be attached to the test workflow - it may be attached to golangci-lint see: dorny/test-reporter#67 https://github.com/orgs/community/discussions/24616 a fork of this dorny/test-reporter has a solution at: phoenix-actions/test-reporting#21
- Since we don't yet have SDLC pipeline projects for Go libraries or for public projects, add in some limited CI validation for PRs to this repo including: * A build and test stage that generates binaries with the Makefile *and* runs make test-coverage to produce coverage (not currently used in CI) Also uploads these as artifacts * Linting through the golangci-lint Github Action - NOTE: intially use dorny/test-reporter which produces Github checks, which by design doesn't always attach to the right workflow - results may show up with golangci-lint. See dorny/test-reporter#67 https://github.com/orgs/community/discussions/24616 To resolve this, switch to a fork that uses summary instead: phoenix-actions/test-reporting#21
This PR allows adds the option
output-to
, which can be set tostep-summary
(orchecks
). This circumvents the issue mentioned in the README under "Github limitations"