Mirrors/Win11Debloat
1
0
Fork 0
mirror of https://github.com/Raphire/Win11Debloat.git synced 2026-04-03 14:06:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update CONTRIBUTING.md

Browse Source
This commit is contained in:
Raphire
2026-03-08 02:14:28 +01:00
parent ea9b3ce02b
commit 9467d6cb7b
1 changed files with 1 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
.github/CONTRIBUTING.md vendored
View File

@@ -92,14 +92,6 @@ Win11Debloat/
- Try to limit your indentation to a max of 4-5 levels, if possible. - Try to limit your indentation to a max of 4-5 levels, if possible.
- Use [Segoe Fluent Icon Assets](https://learn.microsoft.com/en-us/windows/apps/design/iconography/segoe-fluent-icons-font) for icons. - Use [Segoe Fluent Icon Assets](https://learn.microsoft.com/en-us/windows/apps/design/iconography/segoe-fluent-icons-font) for icons.
### Testing Registry Changes
1. **Backup Registry**: Always create a system restore point
2. **Test Manually**: Test the registry changes manually first
3. **Verify Undo**: Test that the undo registry file properly reverts changes
4. **Verify Sysprep**: Test that the Sysprep registry file properly applies changes for new users
5. **Check Side Effects**: Ensure no unintended consequences
### Common Pitfalls ### Common Pitfalls
Avoid these common mistakes when contributing: Avoid these common mistakes when contributing:
@@ -342,7 +334,7 @@ UI Groups allow features to be grouped together in the GUI with a combobox (drop
- Go to the original Win11Debloat repository - Go to the original Win11Debloat repository
- Click "New Pull Request" - Click "New Pull Request"
- Select your fork and branch - Select your fork and branch
- Provide a clear description of your changes - Provide a clear description of your changes, including references to the registry keys used
- Reference any related issues - Reference any related issues
4. **Respond to feedback**: Be prepared to make adjustments based on code review feedback. 4. **Respond to feedback**: Be prepared to make adjustments based on code review feedback.