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.
In #131, first, and then in #156, a change was proposed to support the same functionality as CircleCI, where a terminal is open concurrent to the running job's steps. And as I mentioned in the latter PR, I have found that feature quite useful (implementing it "manually", by having two
shell: bash
steps).Here is a very small PR to propose a much simpler UI but essentially offer the same feature: by setting the input
detached: true
, theaction-tmate
step will start a new, detachedtmate
session, print the information how to connect to that, and then continue with the workflow job's next steps, keeping thetmate
session running. In the post-job phase,action-tmate
will then wait for the session to end (or, if nobody connected to the session within 10 minutes of that post-job Action, terminate anyway).Sadly, this PR results in warnings about the usage of the
save-state
command that would only be solved by upgrading to@actions/core
1.10.0. However, in #152 we tried that and the same blockers are still there. So I'll punt on that, for now.