33 lines
903 B
Markdown
33 lines
903 B
Markdown
# WORK FLOW
|
|
|
|
## Team VN
|
|
|
|
_Create Issue: include feature & bug
|
|
|
|
_Prepare all assets for that feature & bug.
|
|
|
|
_Update documentation.
|
|
|
|
## Team Italy
|
|
|
|
_Using gitea: drag issue from : ToDo -> In Progress -> Done (Git auto change to done)
|
|
|
|
_Support teamVN feedback about documentation.
|
|
|
|
|
|
## GIT FLOW
|
|
|
|
**Team Italy** after finish any feature or bug.
|
|
:::tip
|
|
Create PullRequest: Title format should be: `Close #{Issue ID}: {content}` (Following this format will help automate the closing of linked issues when the pull request is merged).
|
|
:::
|
|
|
|
**Team VN** will try to review and merge as soon as possible.
|
|
|
|
|
|
:::tip
|
|
Sometimes **team VN** still not merge PullRequest and **team Italy** want to do next issue.
|
|
To avoid conflicts, recommend using prefabs for features and notifying team members whenever update the SCENE.
|
|
|
|
Normally, if PullRequest1 is good and merge to develop. PullRequest2 will not conflict.
|
|
::: |