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

Delete page "1.5%29-GitHub-Guidelines-3"

Darklighter
2025-02-26 23:37:16 +00:00
parent 670d85c940
commit 579a15660c
1 changed files with 0 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
1.5%29-GitHub-Guidelines-3.md

@@ -1,33 +0,0 @@
8. Refer to Issues or Pull Requests
```If your commit addresses an open issue or references a pull request, include the issue number in the commit message (using # followed by the issue number).
Example:
Good: "Fix issue #45: Resolve crashing issue on app startup"
Bad: "Fix crashing issue"```
9. Avoid Personal or Ambiguous Messages
```Avoid using personal pronouns like "I" or "We" in commit messages.
Commit messages should be professional and clearly communicate the change to other team members.
Example:
Good: "Refactor data processing function"
Bad: "I refactored the data processing function"```
10. Keep it Relevant to the Codebase
```Commit messages should always be relevant to the changes made in the code. Don't use commit messages for unrelated updates, like changes to the documentation, unless the commit is specifically related to that task.
Example:
Good: "Update CSS styling for homepage buttons"
Bad: "Update README"
Example of a Good Commit Message:
Commit Summary: "Add search bar functionality to the homepage"
Description:
Implemented search bar for better user experience.
Linked search functionality to the backend API.
Updated front-end to handle dynamic search queries.```