Articles, notes and random thoughts on Software Development and Technology
Previous script for setting git branch in bash shell is here.
For zsh, here’s an approach from this gist – add to your ~/.zshrc:
function parse_git_branch() {
git branch 2> /dev/null | sed -n -e 's/^\* \(.*\)/[\1]/p'
}
COLOR_DEF=$'\e[0m'
COLOR_USR=$'\e[38;5;243m'
COLOR_DIR=$'\e[38;5;197m'
COLOR_GIT=$'\e[38;5;39m'
setopt PROMPT_SUBST
export PROMPT='${COLOR_USR}%n ${COLOR_DIR}%~ ${COLOR_GIT}$(parse_git_branch)${COLOR_DEF} $ '
Tags are useful to mark specific versions or releases of your code in a repo on a given branch. To tag everything on the current branch, use:
git tag new-tag-name
To push a new tag to a remote repo, you can either push all tags (which is not recommended):
git push remote-name --tags
or push a specific tag:
git push remote-name tag-name
More example in this SO question.
From : https://gist.github.com/ankurk91/2efe14650d54d7d09528cea3ed432f6d
#Git branch in prompt.
parse_git_branch() {
git branch 2> /dev/null | sed -e '/^[^]/d' -e 's/ (.*)/ (\1)/'
}
export PS1="\u@\h \W[\033[32m]\$(parse_git_branch)[\033[00m] $ "
Want to find out more about these escaped codes and ANSI escape sequence color codes, here’s a good reference.
Following on from this post, Runners are added per project (unless they are shared). If you’re configuring a new project and haven’t created a new runner and assigned it to your project, you’ll see this:
Add a new runner per the steps in the previous article.