Compare commits

...

2 Commits

Author SHA1 Message Date
Gabi
4ab1681eb8 Added dorion to applications.json (#4340) 2026-04-08 12:33:12 -05:00
Gabi
ed6ee897d5 Added language support warning to CONTRIBUTING.md (#4342) 2026-04-08 11:19:10 -05:00
2 changed files with 12 additions and 1 deletions

View File

@@ -21,12 +21,14 @@
* Pull requests are now handled directly on the **MAIN branch**. This was done since we can now select specific releases to launch via releases in GitHub. * Pull requests are now handled directly on the **MAIN branch**. This was done since we can now select specific releases to launch via releases in GitHub.
* If you're doing code changes, then you can submit a PR to the `main` branch, but I am very selective about these. * If you're doing code changes, then you can submit a PR to the `main` branch.
!!! warning "Important" !!! warning "Important"
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! 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!
Do not open a pull request that adds support for other languages to WinUtil for now, until we decide how we want to move forward with language support.
* 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 `tweaks` section and corresponding `undo tweak`, 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. * 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 `tweaks` section and corresponding `undo tweak`, 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.
* By following these guidelines, we can maintain a high standard of quality and ensure that the codebase remains organized and well-documented. * By following these guidelines, we can maintain a high standard of quality and ensure that the codebase remains organized and well-documented.

View File

@@ -528,6 +528,15 @@
"link": "https://ntlite.com", "link": "https://ntlite.com",
"winget": "Nlitesoft.NTLite" "winget": "Nlitesoft.NTLite"
}, },
"dorion": {
"category": "Communications",
"choco": "na",
"content": "Dorion",
"description": "Tiny alternative Discord client with a smaller footprint, snappier startup, themes, plugins and more!",
"link": "https://github.com/SpikeHD/Dorion",
"winget": "SpikeHD.Dorion",
"foss": true
},
"ditto": { "ditto": {
"category": "Utilities", "category": "Utilities",
"choco": "ditto", "choco": "ditto",