macOS
Homebrewverified · 100%
brew install git-octopuslocal Homebrew formula metadata
brew / rank 5291
Install git-octopus with Homebrew, dnf, Nix
Continuous merge workflow. Version 1.4 via Homebrew; verified 2026-05-19. Also installable with nix: nix profile install nixpkgs#git-octopus.
install
Additional install commands
Linux
Fedora dnfverified · 92%
sudo dnf install git-octopusFedora Rawhide package metadata · git-octopus · source: dl.fedoraproject.org
Nixverified · 92%
nix profile install nixpkgs#git-octopusnixpkgs package indexes · pkgs/by-name/gi/git-octopus/package.nix · source: api.github.com
overview
Package summary
Continuous merge workflow
Project links
Commands and aliases
- git-apply-conflict-resolution
- git-conflict
- git-octopus
history
Project history and usage
git-octopus is a Git extension for a continuous merge workflow based on feature branches. It adds git octopus for pattern-based multi-branch merges and git conflict for recording conflict resolutions that can be reused.
Project history
LesFurets published the repository on GitHub in 2014 and described the project as an attempt to reconcile feature branching with continuous integration and delivery. The first GitHub release, v1.0, appeared in 2015, followed by releases that added conflict-resolution support, documentation improvements, and chunk-mode changes.
Adoption history
Compared with the single-purpose Git helpers in this batch, git-octopus had a broader process pitch: its README describes CI jobs that merge all feature branches with the mainline and force-push the assembled result to an octopus branch for build and deployment. Packaging reached Homebrew, Fedora/RHEL-style RPM instructions, and Nix, which signals use beyond a private script.
How it is used
Teams use git-octopus to continuously build an integration branch made from many feature branches without making that merge part of long-lived history. When merges fail, git conflict can diagnose conflict pairs and store standard Git refs containing recorded resolutions that can be fetched and pushed.
Why package nerds care
The package matters to Git workflow enthusiasts because it turns Git's native octopus-merge idea into a CI/CD convention with installable commands, manpage-style documentation, release notes, and distribution packaging. It also documents a concrete branch policy: keep the mainline ready to ship, isolate work on small branches, and continuously test their combined result.
Timeline
- 2014: Repository was created on GitHub.
- 2015: v1.0 was released.
- 2015: v1.1 introduced a first step toward conflict resolution.
- 2016: v1.4 was released and RPM packaging notes documented version 1.4 packaging.
- 2017: v2.0 beta releases marked a Go rewrite.
Related projects
- git merge
- continuous integration systems
- feature-branch workflows
Sources
- https://formulae.brew.sh/formula/git-octopus
- https://github.com/lesfurets/git-octopus
- https://lesfurets.github.io/git-octopus/doc/git-conflict.html
- https://lesfurets.github.io/git-octopus/doc/git-octopus.html
- https://raw.githubusercontent.com/lesfurets/git-octopus/master/README.md
- https://raw.githubusercontent.com/lesfurets/git-octopus/master/RELEASE.md
security posture
Risk level: green
narrow executable package without higher-risk signals.
Risk classifier
green risk · low confidence · appliance
Why
- narrow executable package without higher-risk signals
Signals
- metadata:no-higher-risk-signals
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
git-apply-conflict-resolution | executable | indexed executable | Discovered from the local executable index. |
git-conflict | executable | indexed executable | Discovered from the local executable index. |
git-octopus | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version1.4
manager updated2026-05-19
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:git-octopus |
|---|---|
| Version | 1.4 |
| Package manager | Homebrew |
| Homepage | https://github.com/lesfurets/git-octopus |
| Repository | https://github.com/lesfurets/git-octopus |
| Last updated | 2026-05-19T07:47:35-04:00 |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source database matches
Other package-manager records
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
Nix95%
git-octopus
nix profile install nixpkgs#git-octopus- normalized package name match
- Matched by: Git Octopus
dnf95%
git-octopus 2.0-0.4.beta.3.fc45.28
Git commands for continuous delivery
https://github.com/lesfurets/git-octopus
sudo dnf install git-octopus- License: LGPL-3.0-only
- Category: Unspecified
- Architecture: x86_64
- Source Package: git-octopus
- 4 dependencies
- 1 provides
- normalized package name match
- Matched by: Git Octopus
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- cross-ecosystem install command graph
- curated package history
- external package-manager database matches
- pkg.so package database
- pkgdb category and tag curation