1.5) GitHub Guidelines 2 aktualisiert
@@ -34,8 +34,8 @@ Bad: "Fix bugs"```
|
||||
|
||||
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:
|
||||
Good: "Add unit tests for user registration module"
|
||||
Bad: "Add unit tests and refactor login page"```
|
||||
Bad: "Add unit tests and refactor login page"
|
||||
Reference in New Issue
Block a user