work‐routine
-
Set global username/email configuration to identify yourself (dev.machine) from git-server POV:
- Set your username using
git config --global user.name "FIRST_NAME LAST_NAME"- Verify username using
git config --global user.name
- Verify username using
- Set your email address using
git config --global user.email "MY_NAME@example.com"- Verify email address using
git config --global user.email
- Verify email address using
- Set your username using
-
Setup ssh keys in both local-development-machine and git-server as Github.
-
Create new folder (directory) inside any partition other than
C, and call itWorkspace. -
Cloning an existing git repository happens once using
git clone <repository-url>inside your localWorkspacefolder.
-
Before start working on a git repository locally after cloning it on the first time, you have to bring the latest updates to this repository that have been made so far via other co-workers using
git pullthat is executed inside the folder of this repository.
-
Then you have to create a new feature-branch, and switching to it using
git checkout -b feature-branch_ticket-number.
-
On completing the work on this ticket, you have to do the below procedures:
-
Add the completed work to the staging area using
git add . -
Prepare the completed work to be moved to the remote-git-server by adding a descriptive message using
git commit -m "message goes here". -
Move the latest changes you have made locally so far to the remote-git-server using
git push -u origin feature-branch_ticket-number. 
-
Add the completed work to the staging area using
-
Then you have to open a PR following this guideline and wait till it be approved ✅, then you can start working on a new ticket.
If a malfunctioning is detected during testing the ticket from QA staff, then you have to follow this guideline.