Here are a few important shortcuts that help me be more productive throughout the day at work:
Creating aliases for commands.
Using pbcopy.
Using...
For further actions, you may consider blocking this person and/or reporting abuse
I hate this one with a passion. People who have aliases like this are almost always the same people who only ever write one-liner commit messages, no matter how simple or complex the actual commit is.
But what they lose by writing one-liners, they often make up with line length, often going way over the best practice character limit.
I really wish committing with
-mwas just locked for anyone who hasn't been using git for at least 5 years and knows what they're doing.Why would you need multi line commit messages? A commit message should be a name and that's it, leave the details for the PR that will eventually squash all commits into a final frozen commit (which will include all the details)
When browsing the git logs I don't want to have to find the merge commit to get details about what one commit changed. A commit should, when necessary, explain the changes and maybe the reasoning for it. It's painful when I want to find out why a change was made but the commit doesn't explain anything.
Squashing all commits into one is not good practice in my opinion. If you are going to do squashing, do it in a controlled manner with rebase. Taking 10 commits and squashing into 1 loses a ton of information if the commits were well written.
PRs are tied to GitHub. Commit messages are agnostic to which git forge you're using. When I want to see why a change was made, I
git blamethe file, and look at the commit message for that change.Squashing commits should generally be avoided because you lose a lot of information from individual commits.
I think you're a bit too fixated on your own non-standard git workflow there.
I also sometimes use a sort of throw-away git history where some commits are just "fix", that I later intend to clean up with a rebase. If you want to make that your main workflow for every branch, then sure, you can be a lot less thorough with your individual commit messages.
But the "intended", and afaik most common way of using git, is to keep commits atomic, and have their messages describe the change that was made. If the reason for a change isn't obvious from just looking at the code and maybe some extra context from previous commits (or from a later merge commit), then that should be explained in the commit message.
Putting too much information in a single commit really just makes it hard to reason about the individual parts that make up a larger change, like introducing a new feature. If all you see in your git history is "add feature X", then that's hardly better than a normal change log, and you lose all the important step-by-step information of how feature X was actually added, what preparations were necessary, etc. as well as the ability to undo individual changes if necessary.
Yeah perhaps my workflow is uncommon. My commits are still atomic however, just at the master branch, not my working branch. And usually extra context lives in the task definition that originated the changes, which is usually linked in the PR which ultimately forma part of the master commit description.
bash aliases are great, but for git sub commands I personally prefer (and recommend) to use
[alias]section in.gitconfig.🫣 instead of aliasing directories, use zoxide. After the first
cd /this/is/batmanthen you can just doz batman.🎉😎 See CLI tools you cant live without
I have these ones in my zshrc, near others for Linux
alias G=’| grep --color=autogitcommit(){
# All element except the last one
git add "${@: 1:-1}"
# Last element
git commit -m "${@: -1:1}"
}
alias ggc=gitcommit
Adding all alias in the plugin git in zsh :)
For a good Linux alternative to
pbcopyandpbpaste, try outxclip.And if you're using Termux on Android,
termux-clipboard-getandtermux-clipboard-setgive you access to the Android clipboard.Some problems here:
aliases
This doesn't do what you think it does:
The
$1isn't expanded to anything in your alias. It works because your message goes at the end of the line. You can see this if you try a little test:If you want to use substitution then you should be using a function or a script, not an alias.
pbcopy
You go on to say
But you don't provide any guides for Linux. If you want similar functionality to
pbcopy, you're probably looking forxselorxclipbut ymmv.reverse search
This isn't a command at all! It's a feature of the input library. I think from memory this is
readlinemost of the time. It gives you a bunch of nice features like the reverse search you mentioned, and it will work that way in any application which uses that library. This means that you can be using something like themysqlclient, or a programming language REPL and there's a reasonable chance you have the same super powers there too.With ZSH you can put all of your custom aliases in a custom file. Default location is ~/.oh-my-zsh/custom.
I use ~/.oh-my-zsh/custom/zsh-aliases
I preface my aliases with my initials and a - , mw- in my case.
Then I can type mw- [tab] to see all of my aliases.
I also created an alias that opens the custom alias file.
As mentioned above ZSH includes a lot of aliases and you can use the "aliases" plug in to display all installed ZSH aliases
This is what my ZSH plugins looks like:
plugins=(
git
zsh-completions
zsh-autosuggestions
zsh-syntax-highlighting
history-substring-search
colored-man-pages
aliases
zsh-docker-aliases
)
github.com/ohmyzsh/ohmyzsh/tree/ma...
You are aware that OMZ is not required? Nothing OMZ does can't be done without it, it's all ZSH scripts. Though, yes you can source any file you want in to your
.zshrc(or any shell script).Instead of the
cdalias, on ZSH there is a named directory feature:Thank you for "cal" =)
Wow 😲 these alias commands are awesome 🔥🔥🔥
Thank you so much!
Use OhMyZsh
I have a bunch of useful git shortcuts defined in my .zshrc
Cool Stuff!!
What about
fzf? Do you think it could be a good addition?Cool article - one thing I'd add is to be careful with the encryption within vim. This was removed in neovim for good reason, it's very buggy, unmaintained and doesn't do what it says it is.
Those bonus ones are amazing 👍
Thanks, really helpful!
Thx, helpful ! I didn't know pbcopy. Regarding aliases, the Ohmyzsh plugin already provide a lot of my usual git commands.
Nice tips, for git aliases it is better to put them inside of .gitconfig instead of bash aliases to me and you could just create on bash g as git to make it accessible, have you tried that?
I use zshrc, and it comes with a lot of default git shortcuts, didn't have to do that.
I've been coding for over 10 years now and never thought to alias my projects 😅
Time to alias all my active ones 😈