From 2ced35f6485edb930f9815c0aea3c7a0654fe2d8 Mon Sep 17 00:00:00 2001 From: <> Date: Tue, 1 Oct 2024 19:10:51 +0000 Subject: [PATCH] Deployed db26666 with MkDocs version: 1.6.0 --- contribute/index.html | 2 +- sitemap.xml.gz | Bin 127 -> 127 bytes userguide/index.html | 4 ++-- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/contribute/index.html b/contribute/index.html index 3ed6777b..590be85b 100644 --- a/contribute/index.html +++ b/contribute/index.html @@ -12,4 +12,4 @@ graph TD E --> F[Push Branch]; F --> K[Create Pull Request]; K --> L[Fill out PR template]; - classDef default stroke:#333,stroke-width:4px,font-size:12pt;
Info
This is a diagram to guide you through the process. It may vary depending on the type of change you're making.


Tip
While you can make your changes directly through the Web, we recommend cloning the repo to your device using the application GitHub Desktop (available in WinUtil) to test your fork easily.
Create a new branch and name it something relatable to your changes.
Now you can modify WinUtil to your liking using your preferred text editor.
To test to see if your changes work as intended run following commands in a powershell teminal as admin:
Change the directory where you are running the commands to the forked project.
cd {path to the folder with the compile.ps1}.\Compile.ps1 -run
winutil.ps1 file, like the following:

