Merge pull request #683 from ghost/add-qol

Allow workflows to run by using the REST API or from the Actions tab on GitHub

.github/workflows/linux.yml

@@ -1,6 +1,7 @@
 name: linux_build
 
 on:
+  workflow_dispatch:
   schedule:
     - cron: '0 0 * * *'
   push:

.github/workflows/macos.yml

@@ -1,6 +1,7 @@
 name: macos_build
 
 on:
+  workflow_dispatch:
   schedule:
     - cron: '0 0 * * *'
   push:

.github/workflows/windows.yml

@@ -1,6 +1,7 @@
 name: windows_build
 
 on:
+  workflow_dispatch:
   schedule:
     - cron: '0 0 * * *'
   push:

README.md

@@ -118,7 +118,7 @@ According to the VS Code Marketplace [Terms of Use](https://aka.ms/vsmarketplace
 Please note that some Visual Studio Code extensions have licenses that restrict their use to the official Visual Studio Code builds and therefore do not work with VSCodium. See [this note](https://github.com/VSCodium/vscodium/blob/master/DOCS.md#proprietary-debugging-tools) on the Docs page for what's been found so far and possible workarounds.
 
 ### How are the VSCodium binaries built?
-If you would like to see the commands we run to build `vscode` into VSCodium binaries, have a look at the workflow files in `.github/workflow` (for GNU/Linux and macOS builds) and the `win32-build.yml` file (for Windows builds). These build files call all the other scripts in the repo. If you find something that doesn't make sense, feel free to ask about it [on Gitter](https://gitter.im/VSCodium/Lobby).
+If you would like to see the commands we run to build `vscode` into VSCodium binaries, have a look at the workflow files in `.github/workflow` for Windows, GNU/Linux and macOS. These build files call all the other scripts in the repo. If you find something that doesn't make sense, feel free to ask about it [on Gitter](https://gitter.im/VSCodium/Lobby).
 
 The builds are run every day, but exit early if there isn't a new release from Microsoft.