|
|
|
|
|
by bminor13
1247 days ago
|
|
> shifting default workflows away from the standard client is one of those changes that doesn't serve users There is no "default workflow" for git - Git can be used in a variety of ways; everyone has their own personal preference, and some of these workflows are shaped by interacting with systems like Github/Gerrit/etc. Every place I've ever worked at has either: - a home-grown wrapper around git to make common operations easy
- a recommended set of git aliases around common operations
The fact that Github has created their own to interact with their own system is a net win for individuals/organizations who would otherwise need to spend time scripting their own.Of all the capabilities of the Github CLI, `gh pr checkout` is the only one I use, because it makes it easy to fetch a PR locally by ID without configuring a remote per fork. I'm pretty glad I didn't have to write this myself. |
|
> There is no "default workflow" for git
The default workflow, as in what Github promotes. Github's default, not git's. That's what's meant.