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
We have a customer who uses is-ci to tweak their behavior when building, and they've noticed that we're not supported (which is not a surprise, we're a small SaaS company). I had a look at your code and it looks like you just check for env vars, is there any chance you could add a check for:
RELEASE_COMMIT_SHA
I know we have kind of a generic name, but I think this should be a pretty unique identifier.
The text was updated successfully, but these errors were encountered:
Is it possible to add new default environment variables to the runner? May be something like RELEASE_HUB like other vendors do? And Adding CI=true regardless of vendor identification would be helpful.
And RELEASE_COMMIT_SHA will this be available in the runner for all types of triggers?
Hi,
We have a customer who uses is-ci to tweak their behavior when building, and they've noticed that we're not supported (which is not a surprise, we're a small SaaS company). I had a look at your code and it looks like you just check for env vars, is there any chance you could add a check for:
I know we have kind of a generic name, but I think this should be a pretty unique identifier.
The text was updated successfully, but these errors were encountered: