cli: define GIT_* variables when workflow resides in a git repo #823
Comments
ivotron
added a commit
that referenced
this issue
May 24, 2020
If the workspace directory does not reside within a git repository, assign 'None' to PopperConfig.git_* properties. This in turns results in not defining GIT_* environment variables at all when executing a workflow. fixes #823
ivotron
added a commit
that referenced
this issue
May 25, 2020
If the workspace directory does not reside within a git repository, assign 'None' to PopperConfig.git_* properties. This in turns results in not defining GIT_* environment variables at all when executing a workflow. fixes #823
ivotron
added a commit
that referenced
this issue
May 25, 2020
If the workspace directory does not reside within a git repository, assign 'None' to PopperConfig.git_* properties. This in turns results in not defining GIT_* environment variables at all when executing a workflow. fixes #823
ivotron
added a commit
that referenced
this issue
May 25, 2020
If the workspace directory does not reside within a git repository, assign 'None' to PopperConfig.git_* properties. This in turns results in not defining GIT_* environment variables at all when executing a workflow. fixes #823
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When
popper runis executed inside a repository (try to find a.git/folder in $PWD and parent directories), define variables the following variables and make them available inside steps:GIT_COMMITGIT_SHORT_SHAGIT_BRANCHThe text was updated successfully, but these errors were encountered: