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.

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

tee output to console #6

Merged
merged 1 commit into from
Aug 16, 2024
Merged

tee output to console #6

merged 1 commit into from
Aug 16, 2024

Conversation

nickcharlton
Copy link
Owner

@nickcharlton nickcharlton commented Jun 12, 2024

This should hopefully help in debugging. $GITHUB_STEP_SUMMARY is an "environment file" provided by GitHub Actions, so we can treat it just like a file and use tee to append data to it.

Based on an idea by @oscargus raised in #4.

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#adding-a-job-summary
https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#environment-files

This should hopefully help in debugging. `$GITHUB_STEP_SUMMARY` is an
"environment file" provided by GitHub Actions, so we can treat it just
like a file and use `tee` to append data to it.

Based on an idea by @oscargus raised in #4.

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#adding-a-job-summary
https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/workflow-commands-for-github-actions#environment-files
@nickcharlton nickcharlton merged commit 2805447 into main Aug 16, 2024
1 check passed
@nickcharlton nickcharlton deleted the tee-output branch August 16, 2024 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant