`npm run deploy` does not work on Windows

[griffpatch]

Expected Behavior

Deploys the current build to the gh-pages branch in github

Actual Behavior

From github console:

~\Documents\GitHub\scratch-vm [optimisation/reuseStackForNextBlock ↑43]> npm run deploy

> scratch-vm@0.1.0 deploy C:\Users\griffpatch\Documents\GitHub\scratch-vm
> touch playground/.nojekyll && ./node_modules/.bin/gh-pages -t -d playground -m "Build for $(git log --pretty=format:%H -n1)"

'.' is not recognized as an internal or external command,
operable program or batch file.

from node.js console:

C:\Users\griffpatch\Documents\GitHub\scratch-vm>npm run deploy

> scratch-vm@0.1.0 deploy C:\Users\griffpatch\Documents\GitHub\scratch-vm
> touch playground/.nojekyll && ./node_modules/.bin/gh-pages -t -d playground -m "Build for $(git log --pretty=format:%H -n1)"

'touch' is not recognized as an internal or external command,
operable program or batch file.

Operating System and Browser

Windows 10 pro, PC

[rschamp]

@griffpatch As a temporary work around, you could use the infrastructure we have for auto-deploying from Travis. To do so:

• Enable your fork on travis-ci.org
• Add a RELEASE_BRANCHES env variable (in "Settings" for the repo on Travis), set to "develop master" (or "develop master optimisation/reuseStackForNextBlock" in this case) — these are the branches Travis watches and deploys from.
• Create a Github personal access token (from GitHub settings), with read/write repo permissions
• Add a GH_PAGES_REPO env variable, set to https://<personal access token>@github.com/griffpatch/scratch-vm.git — make sure you set "Display value in build log" to off

From then on your pushes to your fork should deploy to your gh-pages branch.

[benajaero]

I don't believe that you can touch a file in windows. It is a bash command.