Group tar's output to prevent it from messing up action logs #94
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.
Hello maintainers, Please let me know if this PR is unreasonable.
When running a GitHub workflow, outputs of an action will be automatically grouped by step, but when an action is used as a component of another composite action, outputs from different components have no difference, so authors often use
echo ::group::Foo
andecho ::endgroup::
to distinguish them.So when this action is used in composite action (in this case, it is sphinx-notes/pages), the output of
tar
command messes up logs (especially when there are many files to be archived).For example:
(The remaining two thousand lines are not displayed…)
So I patch this action, re-run the job, and everything goes well.
In addition, maybe the IO flush policy of grouped messages is different, and the running duration is accelerated by 1 minute.