-
Branch : Use a branch to isolate development work without affecting other branches in the repository. For more details click on this link
Create a new git branch
$ git branch <new-branch>
-
Status: The status API allows external services to mark commits with an error, failure, pending, or success state, which is then reflected in pull requests involving those commits. For know more details click on this link
Check the status of the repository
$ git status
-
Staged :To stage a changed or modified file, run
git add <file_path>.<ext>
To stage all modified files, run
git add .
For more details click on this link
-
Commit : The commits API allows you to list, view, and compare commits in a repository. You can also interact with commit comments and commit statuses.
For commiting the changes.
$ git commit -m "<your message here>"
For more details click on this link
Pushing commits to a remote repository
$ git push <REMOTENAME> <BRANCHNAME>
For more details click on this link
-
Pull requests : Tell others about changes you've pushed to a branch in a repository on GitHub. For more details click on this link
(i) For how to create the pull request click on this link
(ii) Creating a pull request from a fork : You can create a pull request to propose changes you've made to a fork of an upstream repository.
For know how to create a pull request from a fork click on this link
Why merge conflict occurs and how to resolve that conflict can go through the given links:
After creating pull request perform the following steps
- Self Assign : On the right hand side under the 'Assignees' click on 'assign-yourself'
-
Assigning Ready to review label : On right hand side under assignees you will find 'Labels'. Click on 'Labels' and select 'status : ready for review'
-
Assigning Reviewers for review : On the right hand side above 'Assignees' you can find 'Reviewers'. Click on 'Reviewers' and select 'team-portal-reviewers'