</span></code></pre></div><divclass="admonition bug"><pclass=admonition-title>Keep in mind</p><p>This is a pre-release and should be treated as such. It exists for developers to test the utility and report or fix bugs before they get added to the stable release. Don't use it in production!</p></div><h2id=issues>Issues<aclass=headerlinkhref=#issuestitle="Permanent link">¶</a></h2><ul><li>If you encounter any challenges or problems with the script, I kindly request that you submit them via the "Issues" tab on the GitHub repository. By filling out the provided template, you can provide specific details about the issue, allowing me (and others in the community) to promptly address any bugs or consider feature requests.</li></ul><h2id=contribute-code>Contribute Code<aclass=headerlinkhref=#contribute-codetitle="Permanent link">¶</a></h2><ul><li><p>Pull requests are now handled directly on the <strong>MAIN branch</strong>. This was done since we can now select specific releases to launch via releases in GitHub.</p></li><li><p>If you're doing code changes, then you can submit a PR to <code>main</code> branch, but I am very selective about these.</p></li></ul><divclass="admonition warning"><pclass=admonition-title>Important</p><p>Do not use a code formatter, make massive amounts of line changes, or make multiple feature changes. EACH FEATURE CHANGE SHOULD BE IT'S OWN PULL REQUEST!</p></div><ul><li><p>When creating pull requests, it is essential to thoroughly document all changes made. This includes, but is not limited to, documenting any additions made to the <code>tweaks</code> section and corresponding <code>undo tweak</code>, so users are able to remove the newly added tweaks if necessary, and comprehensive documentation is required for all code changes. Document your changes and briefly explain why you made your changes in your Pull Request Description. Failure to adhere to this format may result in the denial of the pull request. Additionally, any code lacking sufficient documentation may also be denied.</p></li><li><p>By following these guidelines, we can maintain a high standard of quality and ensure that the codebase remains organized and well-documented.</p></li></ul><divclass="admonition note"><pclass=admonition-title>Note</p><p>When creating a function, please include "WPF" or "WinUtil" in the file name so it can be loaded into the runspace.</p></div><h2id=walk-through>Walk through<aclass=headerlinkhref=#walk-throughtitle="Permanent link">¶</a></h2><ul><li>This is a guide for beginners. If you are still having issues, look at the following official GitHub documentation:<ul><li><ahref=https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/about-commits>Commit through WEB</a></li><li><ahref=https://docs.github.com/en/desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project-in-github-desktop#about-commits>Commit through GitHub Desktop</a></li><li><ahref=https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request>Create a Pull Request</a></li></ul></li></ul><h3id=overview>Overview<aclass=headerlinkhref=#overviewtitle="Permanent link">¶</a></h3><preclass=mermaid><code>%%{init: {"flowchart": {"curve": "cardinal"}} }%%
classDef default stroke:#333,stroke-width:4px,font-size:12pt;</code></pre><divclass="admonition info"><pclass=admonition-title>Info</p><p>This is a diagram to guide you through the process. It may vary depending on the type of change you're making.</p></div><h3id=fork-the-repo>Fork the Repo<aclass=headerlinkhref=#fork-the-repotitle="Permanent link">¶</a></h3><ul><li>Fork the WinUtil Repository <ahref=https://github.com/ChrisTitusTech/winutil>here</a> to create a copy that will be available in your repository list.</li></ul><p><imgalt="Fork Image"src=../assets/Fork-Button-Dark.png#only-dark></p><p><imgalt="Fork Image"src=../assets/Fork-Button-Light.png#only-light></p><h3id=clone-the-fork>Clone the Fork<aclass=headerlinkhref=#clone-the-forktitle="Permanent link">¶</a></h3><divclass="admonition tip"><pclass=admonition-title>Tip</p><p>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.</p></div><ul><li>Install GitHub Desktop if it is not already installed.</li><li>Log in using the same GitHub account you used to fork WinUtil.</li><li>Choose the fork under "Your Repositories" and press "clone {repo name}"</li><li><p>Create a new branch and name it something relatable to your changes.</p></li><li><p>Now you can modify WinUtil to your liking using your preferred text editor.</p></li></ul><h3id=testing-your-changes>Testing your changes<aclass=headerlinkhref=#testing-your-changestitle="Permanent link">¶</a></h3><ul><li><p>To test to see if your changes work as intended run following commands in a powershell teminal as admin:</p></li><li><p>Change the directory where you are running the commands to the forked project.</p></li><li><code>cd {path to the folder with the compile.ps1}</code></li><li>Run the following command to compile and run WinUtil:</li><li><code>.\Compile.ps1 -run</code></li></ul><p><imgalt=Compilesrc=../assets/Compile.png></p><ul><li>After seeing that your changes work properly, feel free to commit the changes to the repository and make a PR. For help on that, follow the documentation below.</li></ul><h3id=committing-the-changes>Committing the changes<aclass=headerlinkhref=#committing-the-changestitle="Permanent link">¶</a></h3><ul><li>Before committing your changes, please discard changes made to the <code>winutil.ps1</code> file, like the following:</li></ul><p><imgalt="Push Commit Image"src=../assets/Discard-GHD.png></p><ul><li>Now, commit your changes once you are happy with the result.</li></ul><p><imgalt="Commit Image"src=../assets/Commit-GHD.png></p><ul><li>Push the changes to upload them to your fork on github.com.</li></ul><p><imgalt="Push Commit Image"src=../assets/Push-Commit.png></p><h3id=making-a-pr>Making a PR<aclass=headerlinkhref=#making-a-prtitle="Permanent link">¶</a></h3><ul><li>To make a PR on your repo under a new branch linking to the main branch, a button will show and say Preview and Create pull request. Click that button and fill in all the information that is provided on the template. Once all the information is filled in correctly, check your PR to make sure there is not a WinUtil.ps1 file attached to the PR. Once everything is good, make the PR and wait for Chris (the maintainer) to accept or deny your PR. Once it is accepted by Chris, you will be able to see your changes in the "/windev" build.</li><li>If you do not see your feature in the main "/win" build, that is fine. All new changes go into the /windev build to make sure everything is working OK before going fully public.</li><li>Congratulations! You just submitted your first PR. Thank you so much for contributing to WinUtil.</li></ul><asideclass=md-source-file><spanclass=md-source-file__fact><spanclass=md-icontitle="Last update"><svgxmlns=http://www.w3.org/2000/svgviewbox="0 0 24 24"><pathd="M2113.1c-.10-.3.1-.4.2l-112.12.11-1c.2-.2.2-.60-.8l-1.3-1.3c-.1
