drifty/comaps
1
0
Fork 0
mirror of https://codeberg.org/comaps/comaps synced 2026-01-04 11:53:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

[docs] Update docs about default git branch

Browse Source 
Signed-off-by: jeanbaptisteC <jeanbaptistec@noreply.codeberg.org>
This commit is contained in:
Jean-Baptiste
2025-05-11 11:04:01 +02:00
parent 8f4589edfe
commit 4f53fdea48
15 changed files with 40 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/PR_GUIDE.md
View File

@@ -40,7 +40,7 @@
- Functions and methods should not be long. In most cases, it's good if the whole body of a function or method fits on the monitor. It's good to write a function or a method shorter than 60 lines
- Source files should not be very long
- If you are solving a big task it's worth splitting it into subtasks and develop one or several PRs for every subtask.
- If it's necessary to make a big change list which should be merged to master at once, it's worth creating a branch and make PRs on it. Then to make PR with all commits of the branch to the master
- If it's necessary to make a big change list which should be merged to main at once, it's worth creating a branch and make PRs on it. Then to make PR with all commits of the branch to the main
- In most cases refactoring should be done in a separate PR
- If you want to refactor a significant part of the code base, it's worth discussing it with all developers before starting work
- It's worth using the 'Resolve' conversation button to minimize the list of comments in a PR