x-motemen/ghq

Remote repository management made easy

View on GitHub ↗Jump to charts ↓Open shareable report →

x-motemen/ghq has 3.5k+ stars and 200+ forks on GitHub, is written in Go, and was last pushed on Oct 13, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 18th, 2026
Created on February 5th, 2013
Open Issues & Pull Requests: 41 (+0)
GitHub issues: Enabled
Number of forks: 210
Total Stargazers: 3,790 (+0)
Total Subscribers: 34 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 21.3 days
Mean response time: 147.9 days
90th percentile: 494.8 days
Tracked items: 30

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 900 days
Stale 30+ days: 15
Stale 90+ days: 13

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • copilot (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

ghq is a command-line tool for managing local clones of remote repositories organized by their source URL structure.

The tool solves the problem of scattered repository clones across a filesystem by providing a consistent directory structure similar to how Go's package management works. When you clone a repository using ghq get, it automatically places the clone in a directory hierarchy based on the repository's host and path, defaulting to ~/ghq. For example, cloning a GitHub repository creates a path like ~/ghq/github.com/username/project. The tool supports multiple version control systems including Git and Mercurial, and offers specialized cloning modes such as shallow clones, bare clones, and partial clones with blobless or treeless filtering for Git repositories.

Developers should adopt ghq if they frequently work with multiple remote repositories and want a standardized way to organize them locally. It suits projects where team members need to maintain consistent repository locations or where tooling depends on predictable clone paths. The tool is particularly valuable for those who clone repositories across different hosts and want to query or manage them as a collection. The README does not compare ghq to alternative tools, so no comparative guidance can be offered.

The project maintains active test coverage tracking and automated testing on its primary branch. Development activity shows consistent attention to the codebase with regular updates and maintenance of the tool's core functionality.