You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After some experiments, it seems that path argument has restrictions on what values can be used. That is, I have tried making checkout to clone the repo into GOPATH workspace, e.g. I required the clone path to be exactly $GOPATH/src/github.com/<owner>/<repo>, but none of the following worked as expected:
Both following variants fired an error that looked like the value of the path couldn't be absolute:
With the above configuration, I could use env: GOPATH: ${{ runner.workspace }} in the subsequent run steps. See the full example in the PR profefe/profefe#34
That's being said, the restrictions for path requires some clarification.
The text was updated successfully, but these errors were encountered:
After some experiments, it seems that
path
argument has restrictions on what values can be used. That is, I have tried making checkout to clone the repo intoGOPATH
workspace, e.g. I required the clone path to be exactly$GOPATH/src/github.com/<owner>/<repo>
, but none of the following worked as expected:Both following variants fired an error that looked like the value of the
path
couldn't be absolute:The following produced the same error, even though the path wasn't an absolute:
The following worked, but checkout didn't expand the value of
$GOPATH
:The only way to made it work as I needed was the following
With the above configuration, I could use
env: GOPATH: ${{ runner.workspace }}
in the subsequentrun
steps. See the full example in the PR profefe/profefe#34That's being said, the restrictions for
path
requires some clarification.The text was updated successfully, but these errors were encountered: