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
Currently when simpleGit is configured with an override for a single environment variable:
const git = simpleGit().env('A', 'aaa');
The git child process will be called with an environment of only that override, whereas the default would be to use the process.environment from the containing node process.
This might be intentional, especially in the case of using an object form:
Would cause the git child process to be called with the current state of the process.env object as a base, overridden with the explicitly configured {A: 'aaa'}.
The text was updated successfully, but these errors were encountered:
Currently when
simpleGit
is configured with an override for a single environment variable:The
git
child process will be called with an environment of only that override, whereas the default would be to use theprocess.environment
from the containingnode
process.This might be intentional, especially in the case of using an object form:
But to allow for more flexibility and cleaner calling code, there should be a constructor plugin to allow opting in / out of this behaviour, eg:
Would cause the
git
child process to be called with the current state of theprocess.env
object as a base, overridden with the explicitly configured{A: 'aaa'}
.The text was updated successfully, but these errors were encountered: