CI: Use forward-slashes in paths (cross-platform)

Backslashes ("\") can be interpreted as escape characters
on Unix (Linux, macOS). Replace with forward-slashes, "/",
which are interpreted the same (as directory separators) on all OSes,
at least in arguments to commands such as `cd` and `node`.

Author: DeeDeeG

script/vsts/nightly-release.yml

@@ -6,10 +6,10 @@ jobs:
       # This has to be done separately because VSTS inexplicably
       # exits the script block after `npm install` completes.
       - script: |
-          cd script\vsts
+          cd script/vsts
           npm install
         displayName: npm install
-      - script: node script\vsts\get-release-version.js --nightly
+      - script: node script/vsts/get-release-version.js --nightly
         name: Version
         env:
           REPO_OWNER: $(REPO_OWNER)
@@ -40,7 +40,7 @@ jobs:
        #This has to be done separately because VSTS inexplicably
        #exits the script block after `npm install` completes.
       - script: |
-          cd script\vsts
+          cd script/vsts
           npm install
         displayName: npm install
 
@@ -51,7 +51,7 @@ jobs:
         displayName: Download Release Artifacts
 
       - script: |
-          node $(Build.SourcesDirectory)\script\vsts\upload-artifacts.js --create-github-release --assets-path "$(System.ArtifactsDirectory)" --linux-repo-name "atom"
+          node $(Build.SourcesDirectory)/script/vsts/upload-artifacts.js --create-github-release --assets-path "$(System.ArtifactsDirectory)" --linux-repo-name "atom"
         env:
           GITHUB_TOKEN: $(GITHUB_TOKEN)
           ATOM_RELEASE_VERSION: $(ReleaseVersion)

script/vsts/pull-requests.yml

@@ -8,10 +8,10 @@ jobs:
       # This has to be done separately because VSTS inexplicably
       # exits the script block after `npm install` completes.
       - script: |
-          cd script\vsts
+          cd script/vsts
           npm install
         displayName: npm install
-      - script: node script\vsts\get-release-version.js
+      - script: node script/vsts/get-release-version.js
         name: Version
         env:
           REPO_OWNER: $(REPO_OWNER)

script/vsts/release-branch-build.yml

@@ -12,10 +12,10 @@ jobs:
       # This has to be done separately because VSTS inexplicably
       # exits the script block after `npm install` completes.
       - script: |
-          cd script\vsts
+          cd script/vsts
           npm install
         displayName: npm install
-      - script: node script\vsts\get-release-version.js
+      - script: node script/vsts/get-release-version.js
         name: Version
         env:
           REPO_OWNER: $(REPO_OWNER)
@@ -47,7 +47,7 @@ jobs:
       # This has to be done separately because VSTS inexplicably
       # exits the script block after `npm install` completes.
       - script: |
-          cd script\vsts
+          cd script/vsts
           npm install
         env:
           GITHUB_TOKEN: $(GITHUB_TOKEN)
@@ -60,7 +60,7 @@ jobs:
         displayName: Download Release Artifacts
 
       - script: |
-          node $(Build.SourcesDirectory)\script\vsts\upload-artifacts.js --create-github-release --assets-path "$(System.ArtifactsDirectory)" --linux-repo-name "atom-staging"
+          node $(Build.SourcesDirectory)/script/vsts/upload-artifacts.js --create-github-release --assets-path "$(System.ArtifactsDirectory)" --linux-repo-name "atom-staging"
         env:
           GITHUB_TOKEN: $(GITHUB_TOKEN)
           ATOM_RELEASE_VERSION: $(ReleaseVersion)
@@ -75,7 +75,7 @@ jobs:
         condition: and(succeeded(), eq(variables['Atom.AutoDraftRelease'], 'true'), eq(variables['IsReleaseBranch'], 'true'))
 
       - script: |
-          node $(Build.SourcesDirectory)\script\vsts\upload-artifacts.js --assets-path "$(System.ArtifactsDirectory)" --s3-path "vsts-artifacts/$(Build.BuildId)/"
+          node $(Build.SourcesDirectory)/script/vsts/upload-artifacts.js --assets-path "$(System.ArtifactsDirectory)" --s3-path "vsts-artifacts/$(Build.BuildId)/"
         env:
           ATOM_RELEASE_VERSION: $(ReleaseVersion)
           ATOM_RELEASES_S3_KEY: $(ATOM_RELEASES_S3_KEY)