Git Command Not Executed in Windows when Modulizer is executed

[Exnadella]

Hi,

When we are trying to upgrade a polymerfire components from 2.x version to 3.x version, the following error is reported in the Console.

The issue seems to be related to Git not able to execute automatically via Polymer Modulizer.

Unhandled Rejection at: Promise Promise {
Error: polymer-workspace: global "git" command not found. Install git on your machine and then retry.
at C:\Users\flyingcontractor\AppData\Roaming\npm\node_modules\polymer-modulizer\node_modules\polymer-workspaces\src\workspace.ts:62:11
at Generator.next ()
at fulfilled (C:\Users\flyingcontractor\AppData\Roaming\npm\node_modules\polymer-modulizer\node_modules\polymer-workspaces\lib\workspace.js:17:58)
at
at runMicrotasksCallback (internal/process/next_tick.js:121:5)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
at Function.Module.runMain (module.js:695:11)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3 } reason: Error: polymer-workspace: global "git" command not found. Install git on your machine and then retry.
at C:\Users\flyingcontractor\AppData\Roaming\npm\node_modules\polymer-modulizer\node_modules\polymer-workspaces\src\workspace.ts:62:11
at Generator.next ()
at fulfilled (C:\Users\flyingcontractor\AppData\Roaming\npm\node_modules\polymer-modulizer\node_modules\polymer-workspaces\lib\workspace.js:17:58)
at
at runMicrotasksCallback (internal/process/next_tick.js:121:5)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
at Function.Module.runMain (module.js:695:11)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen!