kar
/
sp
1
0
Fork 0
Code Issues 12 Pull Requests 2 Packages Projects 3 Releases 1 Wiki Activity

Merge pull request 'readme add git branch flow' (#5) from staging into test 

Reviewed-on: #5
test
Subhodip Ghosh 2025-03-21 08:02:08 +00:00
parent 0ec897bcd0 fdad72889c
commit 67e50a253a
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -0,0 +1,14 @@
### git flow guide / protocol
# dev - any one is free to create / push to / any experiment on this branch
# staging - it is the stage for all developer. all branchout and push over here.
*start point / fork point is staging, i.e. any fix/feature/improvement - you must start branching out from staging.
*better to name your branch with 'z-' , i.e. z-layout-footer-improvement (z-: identifier for temporary and safe to remove from the central repo -> then the file identifier -> then short info regarding the intent)
*many developers prefer feat/feature_name, i faced issue managing those branch using cli (bsd even alpine) for the slash(/)
## staging must have a automated test and deploy mechanism, so that developers can can always be on the same page regarding build/merge conflict issue
# test - staging to test by tester
# master - test to master by tester after full test
# release - master to release with version tag
final packaging and release