Automic VaultAutomic Vault

brew

git-octopus mit Homebrew, dnf, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für git-octopus in AI-Agent-Workflows.

InstallationsbefehlSicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install git-octopus

local Homebrew formula metadata

Linux

Fedora dnfverifiziert · 92%
sudo dnf install git-octopus

Fedora Rawhide package metadata · git-octopus · Quelle: dl.fedoraproject.org

Nixverifiziert · 92%
nix profile install nixpkgs#git-octopus

nixpkgs package indexes · pkgs/by-name/gi/git-octopus/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

Continuous merge workflow

Befehle und Aliase

  • git-apply-conflict-resolution
  • git-conflict
  • git-octopus

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 1 Plattformziele verfügbar.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
git-apply-conflict-resolutioncliglobales Executable
git-conflictcliglobales Executable
git-octopuscliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version1.4
Manager aktualisiert2026-05-19
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.4

https://github.com/lesfurets/git-octopus

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:git-octopus
Version1.4
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/git-octopus
Homepagehttps://github.com/lesfurets/git-octopus
Repositoryhttps://github.com/lesfurets/git-octopus
Upstream-Dokumentationhttps://lesfurets.github.io/git-octopus/doc/git-conflict.html
LizenzLGPL-3.0-only
Quellarchivhttps://github.com/lesfurets/git-octopus/archive/refs/tags/v1.4.tar.gz
Zuletzt aktualisiert2026-05-19T07:47:35-04:00
Pulseupdated
Bottleverfügbar (auf all)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namegit-octopus
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedyes
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

git-octopus

nix profile install nixpkgs#git-octopus
  • normalized package name match
  • Abgeglichen nach: Git Octopus
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/gi/git-octopus/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
dnf95%

git-octopus 2.0-0.4.beta.3.fc44.27

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 Abhängigkeiten
  • 1 stellt bereit
  • normalized package name match
  • Abgeglichen nach: Git Octopus
Fedora Rawhide package metadata · dl.fedoraproject.org · Fedora Rawhide package metadata: git-octopus from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

Gleicher Workflow

  • git-imergeShares av.db curated category or tags: cli, conflict-resolution, developer-tools, git, merge.
  • git-mediateShares av.db curated category or tags: cli, conflict-resolution, developer-tools, git, git-extension.
  • git-lfsShares av.db curated category or tags: cli, developer-tools, git, git-extension.
  • git-macheteShares av.db curated category or tags: cli, developer-tools, git, git-extension.
  • git-multipushShares av.db curated category or tags: cli, developer-tools, git, git-extension.
  • git-nowShares av.db curated category or tags: cli, developer-tools, git, git-extension.

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment