4 ms·
This is one of my favourites, too! And combined with the alias functionality, you can do gh alias set pcw 'pr create --web' and then just use gh pcw
by bewuethr 6y ago
This is one of my favourites, too! And combined with the alias functionality, you can do
gh alias set pcw 'pr create --web'
and then just use
gh pcw
to create a new PR. There's also sufficient smarts around forking or not, depending on write permissions on the upstream repo.
- jhatemyjob 6y agoDo you run this command frequently enough to do an alias? I feel like it'd be better to just have the muscle memory of typing the actual command instead
- bewuethr 6y agoProbably a few times a day? One nice thing about the alias is that it expands and takes more parameters if you want, like gh pcw --base=development It's also super quick to set up an alias, so I don't see why not.
- jhatemyjob 6y agoI used to have a lot of git aliases but then I became dependent on those and forgot the actual git commands that were lying underneath. So whenever I went to a new system I'd have to port my dotfiles or look up the git docs for what the commands were. If a colleague asked me "how do I do X" I had no clue and had to look in my bashrc. Nowadays I only add them if I do it many many times per day. Like "git commit -a -m" for example. I try to keep things as close to stock as I can This type of alias seems on the fence for me, if was like 10x a day I'd definitely be on board but a few times a day is a gray area