ocserve
Independent Rust implementation of the opencode server: same v1 and v2 HTTP/SSE API, tuned SQLite, bounded memory. Verified against the real upstream binaries.
- 29
- Rust
- MIT
- 2 d ago
Multi-repository Git dependency manager with SemVer version resolution, recursive dependency discovery, and cross-platform SSH support. An alternative to Git submodules.
Repo LS-Instruments/RepoHerd, read from GitHub 15 h ago. LS-Instruments has not joined Take My Repo.
LS-Instruments/RepoHerd is a public repo on GitHub by LS-Instruments. Multi-repository Git dependency manager with SemVer version resolution, recursive dependency discovery, and cross-platform SSH support. An alternative to Git submodules. It declares the BSD-3-Clause license on GitHub. It is written mainly in PowerShell, has 3 stars and last changed on 2026-05-09. Nobody has reviewed it on Take My Repo yet, which says nothing about its quality. Read from GitHub on 2026-11-20.
In the maintainer's words. Shown from GitHub; Take My Repo does not keep a copy.
A cross-platform Git dependency management tool that automates cloning, checking out, and version-pinning of multiple repositories from a single JSON configuration. Designed for multi-repo projects where teams need reproducible builds without the complexity of git submodules or monorepo tooling.
RepoHerd resolves recursive dependencies across repository trees, supports both Semantic Versioning (SemVer) and tag-based version pinning, and handles SSH authentication (PuTTY on Windows, OpenSSH on macOS/Linux), Git LFS, and post-checkout script execution.
| Component | Windows 10/11, Server 2016+ | macOS | Linux |
|---|---|---|---|
| PowerShell | 7.6 LTS (side-by-side with 5.1) | 7.6 LTS | 7.6 LTS |
| Git | Git for Windows 2.x+ | Xcode CLI tools or standalone | Distribution package |
| SSH transport | PuTTY/plink + Pageant (.ppk keys) |
OpenSSH (bundled) | OpenSSH (bundled) |
| HTTPS auth | Git Credential Manager (bundled with Git for Windows) | Git Credential Manager | Git Credential Manager or PAT |
| Git LFS | Optional | Optional | Optional |
Install PowerShell 7.6 LTS (installs as pwsh.exe alongside Windows PowerShell 5.1 — existing scripts are unaffected):
winget install Microsoft.PowerShell
Install Git for Windows (includes Git Credential Manager for HTTPS authentication):
Download from git-scm.com or:
winget install Git.Git
Set execution policy (one-time, allows running local scripts):
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
SSH setup (only if accessing repositories via SSH URLs):
RepoHerd uses PuTTY/plink on Windows. See SSH Setup.
Install PowerShell 7.6 LTS:
# Via Homebrew (recommended) brew install powershell # Or via .NET global tool dotnet tool install --global PowerShell
Install Git (may already be installed via Xcode CLI tools):
# Check if installed git --version # Install Xcode CLI tools if needed xcode-select --install
Install Git Credential Manager (for HTTPS authentication to GitHub, Azure DevOps, etc.):
brew install git-credential-manager git-credential-manager configure
SSH setup (only if accessing repositories via SSH URLs):
macOS includes OpenSSH. See SSH Setup.
Install PowerShell 7.6 LTS:
# Ubuntu/Debian sudo apt-get update sudo apt-get install -y powershell # RHEL/CentOS/Fedora sudo dnf install powershell # Or via .NET global tool dotnet tool install --global PowerShell
See Microsoft's Linux installation guide for all distributions.
Install Git:
# Ubuntu/Debian sudo apt-get install git # RHEL/CentOS/Fedora sudo dnf install git
Install Git Credential Manager (for HTTPS authentication):
# Download latest .deb or .rpm from: # https://github.com/git-credential-manager/git-credential-manager/releases sudo dpkg -i gcm-linux_amd64.deb # Debian/Ubuntu git-credential-manager configure
Alternatively, use a Personal Access Token (PAT) for HTTPS repos.
SSH setup (only if accessing repositories via SSH URLs):
Linux includes OpenSSH. See SSH Setup.
Install-Module -Name RepoHerd
Then run from any directory containing a dependencies.json:
Invoke-RepoHerd Invoke-RepoHerd -InputFile "path/to/deps.json" Invoke-RepoHerd -DryRun
Download RepoHerd.ps1, RepoHerd.psm1, and RepoHerd.psd1 to the same directory
Create dependencies.json with your repository configuration
Create git_credentials.json with your SSH key mappings (if using SSH repositories)
Run with pwsh:
pwsh ./RepoHerd.ps1 -InputFile dependencies.json
In non-recursive mode, the script processes only the repositories listed in your main dependencies file. It does not look for or process any nested dependencies.
# If installed from PowerShell Gallery, use Invoke-RepoHerd: Invoke-RepoHerd Invoke-RepoHerd -InputFile "C:\configs\myrepos.json" -CredentialsFile "C:\configs\my_credentials.json" Invoke-RepoHerd -EnableDebug Invoke-RepoHerd -DryRun # If using the script directly: .\RepoHerd.ps1 .\RepoHerd.ps1 -InputFile "C:\configs\myrepos.json" -CredentialsFile "C:\configs\my_credentials.json" .\RepoHerd.ps1 -EnableDebug .\RepoHerd.ps1 -DryRun # Verbose output .\RepoHerd.ps1 -Verbose # Set default API compatibility mode (applies only to Agnostic mode repositories) .\RepoHerd.ps1 -ApiCompatibility Strict # Disable recursive mode (non-recursive mode) .\RepoHerd.ps1 -DisableRecursion # Disable post-checkout script execution .\RepoHerd.ps1 -DisablePostCheckoutScripts # Enable detailed error context for debugging .\RepoHerd.ps1 -EnableErrorContext # Export structured JSON results for CI/CD pipelines .\RepoHerd.ps1 -OutputFile result.json
-InputFile: Path to repository configuration file (default: dependencies.json)-CredentialsFile: Path to SSH credentials file (default: git_credentials.json)-DryRun: Preview operations without making changes-EnableDebug: Create detailed debug log file-Verbose: Show verbose output messages-ApiCompatibility: Default API compatibility mode for Agnostic mode repositories ('Strict' or 'Permissive', default: 'Permissive')-DisableRecursion: Disable recursive dependency processing (default: recursive mode enabled)-DisablePostCheckoutScripts: Disable post-checkout script execution (default: post-checkout scripts enabled)-EnableErrorContext: Enable detailed error context with stack traces (default: simple errors only)-OutputFile: Write structured JSON results to the specified file path (for CI/CD integration)When -OutputFile is specified, a JSON file is written with the results of the checkout operation. The output is guaranteed to be written even on failure, making it safe for CI/CD pipelines. Schema version: 1.0.0.
.\RepoHerd.ps1 -InputFile deps.json -OutputFile result.json
Output structure:
| Field | Type | Description |
|---|---|---|
schemaVersion |
string | JSON schema version ("1.0.0") |
metadata |
object | Execution context: toolVersion, timestamp, dryRun, recursiveMode, maxDepth, apiCompatibility, inputFile, powershellVersion |
summary |
object | success (bool), successCount, failureCount, totalRepositories, postCheckoutScripts (enabled/executions/failures) |
repositories[] |
array | Per-repository results (see below) |
processedDependencyFiles[] |
array | Absolute paths of all dependency files processed |
rootPostCheckoutScripts[] |
array | Post-checkout script tracking for depth-0 (root-level) scripts |
errors[] |
array | Error messages collected during execution |
Repository entry fields:
| Field | Type | Description |
|---|---|---|
url |
string | Repository URL |
path |
string | Absolute checkout path |
dependencyResolution |
string | "SemVer" or "Agnostic" |
status |
string | "success", "failed", or "skipped" |
alreadyCheckedOut |
bool | Whether the repo was already at the correct version |
requestedBy |
string[] | Parent repo URLs or "root-dependency-file" |
tag |
string | Git tag checked out |
requestedVersion |
string? | SemVer version pattern requested (SemVer only) |
selectedVersion |
string? | SemVer version selected (SemVer only) |
postCheckoutScript |
object? | Script tracking: configured, scriptPath, found, executed, status, reason (null if no script configured) |
Post-checkout script status values: "executed", "failed", "skipped", "timeout"
RepoHerd provides two approaches for determining which git tag to checkout for each repository. Both modes examine the available git tags in each repository to make their selection decisions.
Uses Semantic Versioning 2.0.0 rules with the Version field in your dependency file to automatically determine compatible tags.
How it works:
"Version" field in your dependency file for each repositoryVersion Field Patterns in Dependency File:
x.y.z): Selects minimum version that satisfies compatibility
"Version": "2.1.0" in dependency file → Selects 2.1.0, 2.1.1, or 2.2.0 but not 3.0.0x.y.*): Automatically selects latest patch within major.minor
"Version": "2.1.*" in dependency file → Selects latest 2.1.x (e.g., 2.1.5 if available)x.*): Automatically selects latest minor.patch within major
"Version": "2.*" in dependency file → Selects latest 2.x.x (e.g., 2.5.3 if available)Key Benefits:
Uses explicit tag specification with the Tag field in your dependency file to checkout exact versions.
How it works:
"Tag" field in your dependency file for each repositoryTag Field Usage in Dependency File:
Tag): Specifies the precise git tag to checkout
"Tag": "v2.1.0" in dependency file → Checks out exactly tag v2.1.0Key Benefits:
The dependencies.json file contains the specification of the repositories that are your dependencies. This file lists all the repositories you want to checkout and configure, without any credential information:
SemVer Mode Configuration (Recommended):
{
"Post-Checkout Script File Name": "setup-dependencies.ps1",
"Post-Checkout Script File Path": "scripts/build",
"Repositories": [
{
"Repository URL": "https://github.com/user/repo.git",
"Base Path": "repos/my-repo",
"Dependency Resolution": "SemVer",
"Version": "2.1.*",
"Version Regex": "^v(\\d+)\\.(\\d+)\\.(\\d+)$",
"Skip LFS": false
}
]
}Agnostic Mode Configuration:
{
"Repositories": [
{
"Repository URL": "https://github.com/user/repo.git",
"Base Path": "repos/my-repo",
"Tag": "v2.1.0",
"Skip LFS": false
}
]
}Simple Array Format (Legacy Support):
[
{
"Repository URL": "https://github.com/user/repo.git",
"Base Path": "repos/my-repo",
"Dependency Resolution": "SemVer",
"Version": "2.*"
}
]Common Fields:
SemVer Mode Fields:
^v?(\\d+)\\.(\\d+)\\.(\\d+)$)Agnostic Mode Fields:
Post-Checkout Script Fields:
Maps hostnames to SSH key file paths. The key format depends on your platform:
Windows (PuTTY .ppk format):
{
"github.com": "C:\\Users\\username\\.ssh\\github_key.ppk",
"gitlab.com": "C:\\Users\\username\\.ssh\\gitlab_key.ppk",
"ssh://git.internal.corp": "C:\\keys\\internal_key.ppk"
}macOS/Linux (OpenSSH format):
{
"github.com": "/home/username/.ssh/id_ed25519",
"gitlab.com": "/home/username/.ssh/gitlab_rsa",
"ssh://git.internal.corp": "/home/username/.ssh/internal_key"
}[
{
"Repository URL": "https://github.com/microsoft/terminal.git",
"Base Path": "repos/windows-terminal",
"Dependency Resolution": "SemVer",
"Version": "1.19.*"
},
{
"Repository URL": "https://github.com/PowerShell/PowerShell.git",
"Base Path": "repos/powershell",
"Dependency Resolution": "SemVer",
"Version": "7.*",
"Skip LFS": true
}
][
{
"Repository URL": "https://github.com/microsoft/terminal.git",
"Base Path": "repos/windows-terminal",
"Tag": "v1.19.10573.0"
},
{
"Repository URL": "https://github.com/PowerShell/PowerShell.git",
"Base Path": "repos/powershell",
"Tag": "v7.4.1",
"Skip LFS": true
}
][
{
"Repository URL": "https://github.com/org/modern-lib.git",
"Base Path": "libs/modern",
"Dependency Resolution": "SemVer",
"Version": "3.*"
},
{
"Repository URL": "https://github.com/org/legacy-lib.git",
"Base Path": "libs/legacy",
"Tag": "release-2024-01"
}
]When Recursive Mode is enabled (Default) the script automatically discovers and processes nested dependencies. After checking out each repository, it looks for a dependency file (dependencies.json if not specified differently upon script execution) within the root folder of that repository and processes it recursively, with intelligent handling of shared dependencies.
# Default behavior (recursive mode enabled with intelligent tag sorting) .\RepoHerd.ps1 # Disable recursive mode for simple single-file processing .\RepoHerd.ps1 -DisableRecursion # Customize recursive behavior .\RepoHerd.ps1 -MaxDepth 10 # Use strict compatibility mode for Agnostic mode repositories .\RepoHerd.ps1 -ApiCompatibility Strict # Disable post-checkout scripts .\RepoHerd.ps1 -DisablePostCheckoutScripts
When recursive mode processes nested dependencies, a common scenario emerges: the same repository is required by multiple projects with potentially different version requirements. This creates the fundamental challenge that the script's dependency resolution system is designed to solve.
Consider this scenario:
LibraryX at version v2.1.0 (or 2.1.* in SemVer mode)LibraryX but at version v2.0.5 (or 2.0.* in SemVer mode)LibraryX, but they're requesting different versionsWhen the script encounters LibraryX for the second time, it faces a critical decision: which version should be checked out to satisfy both callers?
Main Project Dependencies:
├── ProjectA (requires LibraryX v2.1.0 or 2.1.*)
└── ProjectB (requires LibraryX v2.0.5 or 2.0.*)
When processing recursively:
At this point, the script must determine:
RepoHerd provides two powerful approaches to solve the dependency resolution problem:
Both modes use sophisticated conflict resolution algorithms that consider the compatibility requirements of all callers and select the optimal version that satisfies everyone's needs.
The two dependency resolution modes can be mixed within the same dependency tree.
For detailed documentation on each mode, see:
Per-repository custom dependency file paths and names provide flexibility for different project structures and naming conventions. For details, see Custom Dependency Files.
Post-checkout scripts are PowerShell scripts that execute automatically after a repository is successfully checked out, enabling integration with external dependency management systems. For details, see Post-Checkout Scripts.
Guidelines for protecting credentials, SSH keys, and managing post-checkout script security. For details, see Security Best Practices.
Platform-specific SSH configuration for Windows (PuTTY/Pageant) and macOS/Linux (OpenSSH). For details, see SSH Setup.
Common issues and solutions, debug mode instructions, and enhanced error context. For details, see Troubleshooting.
Step-by-step instructions for upgrading between RepoHerd versions (6.2.x to 7.0.0, 7.0.0 to 7.1.0). For details, see Version Migration Guide.
Links to in-depth guides on migrating dependency trees to RepoHerd and tool comparisons. For details, see Advanced Topics.
This project is licensed under the BSD 3-Clause License - see the LICENSE file for details.
Contributions are welcome! Please feel free to submit a Pull Request.
Originally developed by LS Instruments AG for managing complex multi-repository projects.
Co-authored with Claude (Anthropic) through collaborative development.
LS-Instruments/RepoHerd is a public repo on GitHub by LS-Instruments. Multi-repository Git dependency manager with SemVer version resolution, recursive dependency discovery, and cross-platform SSH support. An alternative to Git submodules.
It declares the BSD-3-Clause license on GitHub.
Its maker tagged it for macOS, Windows and Linux, or as Docker or cross-platform. That is declared by the maker; Take My Repo has not tested it.
Open "Take it" on its page: Take My Repo writes an install plan for your machine and hands it to your AI agent (Claude Code, Codex or Cursor), which asks you before each step. Take My Repo has not tested it on any machine.
Its last change on GitHub was on 2026-05-09. Take My Repo does not judge from that whether it is maintained.
Nobody has reviewed it on Take My Repo yet, which says nothing about its quality.
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
Flutter makes it easy and fast to build beautiful apps for mobile and beyond

A dependency management library inspired by SwiftUI's "environment."

Next-generation torrent client in Rust, with a universally compatible WebUI/API (including backwards compatibility with qbittorrent, rtorrent, transmission, deluge & more).
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype to production without rebuilding the stack.

MVC-Actors: LabVIEW Actor Framework extension implementing Model-View-Controller patterns with bidirectional event publisher/subscriber mechanism and GUI management tools.

A library that extends the Actor Framework to allow for async method execution

A library implementing a high-level actor-based implementation of WebSocket communication.
A library implementing the WebSocket protocol including support for resource names.
Improved Actor Framework Message Maker Supporting Interfaces

This page is also available as structured data, with the same sources and dates.
/api/v1/resources/gh/LS-Instruments/RepoHerdTake My Repo has not tested this on your machine. Requirements come from the project's own documentation.