From 336bfce8fd3c3cc020873f2bf309e77520cacab5 Mon Sep 17 00:00:00 2001
From: wdkse <73613036+wdkse@users.noreply.github.com>
Date: Sun, 28 Mar 2021 17:07:35 -0400
Subject: [PATCH 1/2] workflows manual trigger via dispatch event

---
 .github/workflows/linux.yml   | 1 +
 .github/workflows/macos.yml   | 1 +
 .github/workflows/windows.yml | 1 +
 3 files changed, 3 insertions(+)

diff --git a/.github/workflows/linux.yml b/.github/workflows/linux.yml
index 3b18e25..c08e0a9 100644
--- a/.github/workflows/linux.yml
+++ b/.github/workflows/linux.yml
@@ -1,6 +1,7 @@
 name: linux_build
 
 on:
+  workflow_dispatch:
   schedule:
     - cron: '0 0 * * *'
   push:
diff --git a/.github/workflows/macos.yml b/.github/workflows/macos.yml
index fed6689..c30762b 100644
--- a/.github/workflows/macos.yml
+++ b/.github/workflows/macos.yml
@@ -1,6 +1,7 @@
 name: macos_build
 
 on:
+  workflow_dispatch:
   schedule:
     - cron: '0 0 * * *'
   push:
diff --git a/.github/workflows/windows.yml b/.github/workflows/windows.yml
index 9f62d46..bd7ed2d 100644
--- a/.github/workflows/windows.yml
+++ b/.github/workflows/windows.yml
@@ -1,6 +1,7 @@
 name: windows_build
 
 on:
+  workflow_dispatch:
   schedule:
     - cron: '0 0 * * *'
   push:

From c43a4e5136c034e68c8fc64181bd72af5c776c5d Mon Sep 17 00:00:00 2001
From: wdkse <73613036+wdkse@users.noreply.github.com>
Date: Sun, 28 Mar 2021 17:12:41 -0400
Subject: [PATCH 2/2] obsolete win32-build.yml information

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 670a236..c9bcdef 100644
--- a/README.md
+++ b/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.