From 1bc47755a9e1e38e9f4457352b97edcbe0b86929 Mon Sep 17 00:00:00 2001 From: Darklighter Date: Wed, 26 Feb 2025 23:34:07 +0000 Subject: [PATCH] 1.5) GitHub Guidelines 2 aktualisiert --- 1.5%29-GitHub-Guidelines-2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/1.5%29-GitHub-Guidelines-2.md b/1.5%29-GitHub-Guidelines-2.md index 8f34818..9663d24 100644 --- a/1.5%29-GitHub-Guidelines-2.md +++ b/1.5%29-GitHub-Guidelines-2.md @@ -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"``` \ No newline at end of file +Bad: "Add unit tests and refactor login page" \ No newline at end of file