From 3dca1ee43ec5b5d5a320fff98c31ba642e3f23b7 Mon Sep 17 00:00:00 2001 From: Chris Titus Date: Thu, 6 Jun 2024 11:39:49 -0500 Subject: [PATCH] Update README.md --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index a921ad79..c8b43b54 100644 --- a/README.md +++ b/README.md @@ -128,7 +128,9 @@ If you encounter any challenges or problems with the script, I kindly request th ## Contribute Code -To contribute new code, please ensure that it is submitted to the **TEST BRANCH**. Please note that merges will not be performed directly on the MAIN branch. +If you adding, changing, or deleting an Application... submit to **APPLICATIONS branch**. We batch these in at the end of the month. + +If doing a code change and you can submit a PR to main branch, but I am very selective about these. Do not use a code formatter, massive amounts of line changes, and make multiple feature changes. EACH FEATURE CHANGE SHOULD BE IT'S OWN Pull Request! When creating pull requests, it is essential to thoroughly document all changes made. This includes documenting any additions made to the tweaks section and ensuring that corresponding undo measures are in place to remove the newly added tweaks if necessary. Failure to adhere to this format may result in denial of the pull request. Additionally, comprehensive documentation is required for all code changes. Any code lacking sufficient documentation may also be denied.