Twitter | Search | |
Harry Roberts
Create a Git commit template file (left) and link it through your .gitconfig (right) to have a standard commit message format every time.
Reply Retweet Like More
Ben Bodien 12 Jan 17
Replying to @csswizardry
what kind of stuff do you require in your commit messages? Just the ticket/issue reference?
Reply Retweet Like
Harry Roberts 12 Jan 17
Replying to @csswizardry
And if you’re tired of Git throwing you into Vim, add/update this setting to reflect your editor of choice (e.g. atom, subl):
Reply Retweet Like
Harry Roberts 12 Jan 17
Replying to @csswizardry
Also maybe learn Vim because it’s amazing. Who’d pay a small amount for an ‘Introduction to Vim’ screencast series?
Reply Retweet Like
vigo 12 Jan 17
Replying to @csswizardry @fkadev
Reply Retweet Like
Andy Clarke 12 Jan 17
Replying to @csswizardry
Oooh. Me. Me! 😋
Reply Retweet Like
Sebastian De Deyne 12 Jan 17
Replying to @csswizardry
I would!
Reply Retweet Like
Andrew Milne 12 Jan 17
Replying to @csswizardry
definitely!
Reply Retweet Like
Chris Peak 12 Jan 17
Replying to @csswizardry
I already know it very well but second having designers learn it. Makes pairing with devs much easier.
Reply Retweet Like
Chris Mills 12 Jan 17
Replying to @csswizardry
It's also worth setting and as vim in your .zsh/bash[rc] then most applications won't bother asking
Reply Retweet Like
Harry Roberts 12 Jan 17
Replying to @millscj01
Nice tip! Are your dotfiles online? :)
Reply Retweet Like
Chris Mills 12 Jan 17
Replying to @csswizardry
nope I'll sort, I use ansible to install on new machine but was thinking of gnu stow instead, you got any preference?
Reply Retweet Like
Harry Roberts 12 Jan 17
Replying to @millscj01
I’m so old school that I might as well fax them to myself. Just copy/paste from GH. I set up a new machine once every ~3yr :)
Reply Retweet Like
Joren Van Hee 12 Jan 17
Replying to @millscj01 @csswizardry
I use gnu stow, works goood :) Used this blog post a while ago:
Reply Retweet Like
Spatie 12 Jan 17
+1
Reply Retweet Like
Chris Mills 12 Jan 17
Thanks! I will check it out. I mainly fell back on ansible because brew casks and perl modules are painful.
Reply Retweet Like
Harry Roberts 12 Jan 17
Replying to @_martinwolf
Oh cool! I’ll take a look :)
Reply Retweet Like
Joren Van Hee 12 Jan 17
Replying to @millscj01
Have no experience with ansible, but this is how I did my brew stuff:
Reply Retweet Like
Harry Roberts 12 Jan 17
Replying to @_martinwolf
I have huge respect to every developer in the world who has to do most stuff in English; it’s so impressive.
Reply Retweet Like
Harry Roberts 12 Jan 17
Replying to @_martinwolf
But I’m also glad you’re doing German screencasts: it probably helps German developers whose English might not be so good :)
Reply Retweet Like