Clone any of the komli repositories. cd into the directory before running any of the below commands.
It is great if you could create a pullrequest for every changes your want to merge to master. This way we have can have a complete diff(single view) of codebase which was merged to master with the context. Easier to back track releases and the reason why we did some changes. We will plan to make it mandatory soon.
## Pick and commit and hash and go the branch where you want to move this commit to and run the below command
git cherry-pick commit_hash
## Fetch remote branches
git fetch
## Merge remote master branch in current active branch
git merge origin/master
## Fetch and merge
git pull
## Go to master branch
git checkout master
## Create a new branch from master
git checkout -b branch_name
git push origin branch_name
Two tags should be created before merging any branch to master. Tag in master branch referred as prerelease
and the tag in released branch is referred as release
tag.
- Naming convention for
release tag
inreleased
branch_name : YYYYMMDD_release_branch_name - Naming convention for
prelease tag
in master branch : YYYYMMDD_prerelease_branch_name
** Here branch name is referred as the branch name which is supposed to be merged.
## Creating a tag
git tag -a tag_name -m "Comment for the tagging"
## Pushing all newly created tags
git push --tags
## Get all tags available for this repository
git tag --list
let say we have a tag name delete_me
## delete local git tag
git tag -d delete_me
## delete remote git tag not advised
git push origin :refs/tags/delete_me
git checkout master
=> Create prerelease tag here.git checkout branch_name
=> Create release tag here.
## To show last 10 commit history
git log -10
- git rebase (squash, spliting)
- git submodule