I think aliases are a personal choice, someone prefers to use it, and someone prefers to use tab completion.
When I switched from subversion to git, at the beginning I missed the short commands, but finally I started using tab completion.
As author said, aliases are indisposable to run commands with a specific options.
For my daily work, I don't use aliases, but I use "custom" commands for my daily workflow:
git branch-create $JIRA_ISSUE
git branch-sync <--rebase>
git pr
git branch-clean <--remote>
We have more, but I think these ones may be interesting :D
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think aliases are a personal choice, someone prefers to use it, and someone prefers to use tab completion.
When I switched from subversion to git, at the beginning I missed the short commands, but finally I started using tab completion.
As author said, aliases are indisposable to run commands with a specific options.
For my daily work, I don't use aliases, but I use "custom" commands for my daily workflow:
git branch-create $JIRA_ISSUE
creates new branch from the right branch with the right name according our rulesgit branch-sync <--rebase>
Merges or rebases branch from the base branch(it's deducted by the branch name)git pr
simple ncurses interface to open a pull requests, you don't need to specify the base branch againgit branch-clean <--remote>
Cleans local/remote branches which has been merged into masterWe have more, but I think these ones may be interesting :D