I just released gh-get v2.3.0.
gh-get is a GitHub CLI extension that clones repositories into a structured folder layout under ~/github/<owner>/<repo>, similar to ghq.
Here is what is new in this release.
Better Fork Workflow
The --fork flag was introduced in v2.2.0 and let you fork a repository before cloning.
That release cloned your fork into ~/github/<your-username>/<repo>, which meant the clone lived under your username rather than the original owner’s.
This release changes that.
When you fork a repository, gh-get now clones the original into the canonical location ~/github/<owner>/<repo>.
It then renames origin to upstream and adds your fork as origin.
So after running:
gh get --fork britter/gh-get
You end up with a clone at ~/github/britter/gh-get where:
originpoints to your forkupstreampoints to the original repository
This is the remote setup most contributors use when working on open source projects, and now gh-get sets it up automatically.
Upgrade
If you already have gh-get installed, run:
gh extension upgrade get
The full list of changes is in the changelog.

Benedikt Ritter
Gradle & NixOS Consultant
Developer productivity consultant with five years at Gradle Inc. building Develocity, and co-founder of TestLens. Apache Software Foundation member and founder of GradleX. I help engineering teams ship faster through better Gradle build tooling and reproducible NixOS infrastructure.