REM-Freelancer/REM-Mod
4
0
Fork 0
Code Issues 30 Pull Requests Actions Packages Projects Releases Wiki Activity

1.5) GitHub Guidelines 2 aktualisiert

Darklighter
2025-02-26 23:34:23 +00:00
parent 1bc47755a9
commit 65976d80d9
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
1.5%29-GitHub-Guidelines-2.md

@@ -26,16 +26,20 @@ Updated unit tests for new authentication flow.
6. Be Specific and Descriptive 6. Be Specific and Descriptive
```Be specific about the changes: If you're fixing a bug, adding a feature, or refactoring code, be specific about what was modified and how it impacts the project. ```
Be specific about the changes: If you're fixing a bug, adding a feature, or refactoring code, be specific about what was modified and how it impacts the project.
Example: Example:
Good: "Fix image upload issue on mobile devices" Good: "Fix image upload issue on mobile devices"
Bad: "Fix bugs"``` Bad: "Fix bugs"
```
7. Avoid Large, Unfocused Commits 7. Avoid Large, Unfocused Commits
```
Focus each commit on one change: A commit should ideally contain a single logical change, like fixing a bug, adding a feature, or refactoring a part of the codebase. Large commits that combine unrelated changes make it harder to understand the history of the project. Focus each commit on one change: A commit should ideally contain a single logical change, like fixing a bug, adding a feature, or refactoring a part of the codebase. Large commits that combine unrelated changes make it harder to understand the history of the project.
Example: Example:
Good: "Add unit tests for user registration module" Good: "Add unit tests for user registration module"
Bad: "Add unit tests and refactor login page" Bad: "Add unit tests and refactor login page"
```