Clone, build, update, and clean software checked out from Git — with build-system auto-detection so you don't have to know the toolchain.
The Git page works with the source projects on your machine: clone a remote into your workspace, build it (auto-detecting the build system), update to latest, and clean built artifacts when you're done. No terminal marathon needed for regular git-based tools.
target/build output when you're finished.Click Clone Repository in the top-right corner and paste a remote URL (e.g. https://github.com/user/project.git). NeoArch clones it into the managed workspace and auto-detects the build system.
Four stat cards sit below the header:
| Card | What it shows |
|---|---|
| Total Projects | Number of Git repositories in your workspace |
| Updates Available | Projects with new commits on the remote |
| Builds Today | Successful builds completed today |
| Disk Usage | Total space consumed across all projects |
Each project row shows the repo name, build system badge (Cargo, PKGBUILD, etc.), language badge, and status (Clean / Modified / behind by N commits).
Action buttons on every row:
The ⋯ menu gives extra options:
Two panels sit at the bottom of the page:
Build Activity — a live feed of recent builds showing success/failure, project name, and timestamp.
Repository Storage — a donut chart breaking down disk usage per project, with a list of the largest repos underneath.
| Project layout | Detected build |
|---|---|
Cargo.toml |
Cargo (cargo build) |
configure / autogen.sh |
Autotools (./configure && make) |
Makefile |
Make (make) |
meson.build |
Meson (meson setup && ninja) |
go.mod |
Go (go build ./...) |
package.json |
npm (npm run build) |
PKGBUILD |
makepkg |
| anything else | Custom build (you supply the command) |
.pkg.tar.zst. Prefer AUR packages for system installs; they get the security scan.