-
Notifications
You must be signed in to change notification settings - Fork 10
Using git
Nimesh Kavinda edited this page Aug 27, 2021
·
1 revision
- There are two main Branches -
- Development (Default)
- Production
- You need to create a branch for every issue.
- Don’t push your work directly to the dev branch.
- There are two issue types. -
- Features
- Bugs
- Branch naming convention
<issue type>/<github username of the assigne>/<issue number>
- Before creating a pull request, do dev testing - Assume that you are doing coding with connecting API s.
- Name
<issuetype>: <Issue number>
- If your PR is for fixing a bug, you have to mention the root cause.
- If your PR is for a feature, the user story needs to be mentioned.
- Mention the changes you made in your implementation.
- And mention all the Impact areas after you push your work.
Example :
-
Fix: RSVP-1
-
Closes RSVP-1 (link the kanban board issue)
-
Root cause
User sign up does not work
-
What did you do
Fixed the user creation API
-
Impact areas
User signup page
(You can attach screenshots of the working solution as well)