-
Notifications
You must be signed in to change notification settings - Fork 29
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
handle env variables for Github Actions as well #48
Comments
vbatts
added a commit
that referenced
this issue
May 13, 2021
Fixes #48 Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
vbatts
added a commit
that referenced
this issue
May 14, 2021
Fixes #48 Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
vbatts
added a commit
that referenced
this issue
May 14, 2021
Fixes #48 now with logic to detect GITHUB_SHA env variable, let's do a run without the `-range` flag so that path lights up. Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
vbatts
added a commit
that referenced
this issue
May 14, 2021
Fixes #48 now with logic to detect GITHUB_SHA env variable, let's do a run without the `-range` flag so that path lights up. Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
vbatts
added a commit
that referenced
this issue
May 14, 2021
Fixes #48 now with logic to detect GITHUB_SHA env variable, let's do a run without the `-range` flag so that path lights up. Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As folks switch from Travis to Github Actions, lets also account for
GITHUB_SHA
The text was updated successfully, but these errors were encountered: