PHPackages                             tbureck/splitphp - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [DevOps & Deployment](/categories/devops)
4. /
5. tbureck/splitphp

AbandonedArchivedProject[DevOps & Deployment](/categories/devops)

tbureck/splitphp
================

SplitPHP splits monolithic repositories into multiple repositories using splitsh-lite.

v2.0.2(7y ago)11.7kMITPHPPHP ^5.6.0|^7.0

Since Feb 8Pushed 7y ago1 watchersCompare

[ Source](https://github.com/tbureck/splitphp)[ Packagist](https://packagist.org/packages/tbureck/splitphp)[ RSS](/packages/tbureck-splitphp/feed)WikiDiscussions master Synced 2d ago

READMEChangelogDependencies (1)Versions (5)Used By (0)

Welcome to SplitPHP
===================

[](#welcome-to-splitphp)

**SplitPHP** is a little program that will split subtrees from your Git repository and push them to a separate repository. The actual splitting is done using the [splitsh-lite tool by Fabien Potencier](https://github.com/splitsh/lite).

Getting started
---------------

[](#getting-started)

**SplitPHP** is likely to be used on a continuous integration environment like Travis, Jenkins or TeamCity. There are 3 main requirements for the tool to work:

- PHP 7 (recommended) or 5.6
- Git
- [splitsh-lite](https://github.com/splitsh/lite)

Make sure that the `splitsh-lite` command is available by putting its path in the PATH environment variable, so that **SplitPHP** can find it. The same goes for Git, obviously.

Installation
------------

[](#installation)

Installation is easiest done by using Composer. Add `tbureck/splitphp` to your `require-dev` configuration. The `splitphp` program will then be available in your configured `bin` directory.

Usage
-----

[](#usage)

In order to use **SplitPHP**, you need to create a configuration file, which defaults to `splitsh.json`. It defines the subtrees that should be extracted to the other repositories.

### Configuration

[](#configuration)

Example:

```
{
    "common-library": {
        "prefixes": [
            {"key": "src/Library/Common", "value": ""}
        ],
        "target": "git@bitbucket.org:my-organization/my-repository.git",
        "branches": ["master", "dev-1.x"]
    }
}
```

The key of an object is a simple name for easy identification. The object defines 3 properties:

**prefixes** is a list of key-value pairs that map the monolith path to the standalone repository path (empty path means root directory)

**target** specifies the target standalone repository. Make sure that your CI server has write access to this repository.

**branches** is a list of branches that the split should be done for.

You can specify as many subtrees as you like, they will be processed in that order.

### Running the split

[](#running-the-split)

In order to run the split, you simply need to call the binary and pass the current branch:

```
bin/splitphp master

```

In TeamCity, you can dynamically pass the current branch by using a specific variable. Check your CI server's documentation for how to do this, if you're using a different system:

```
bin/splitphp %vcsroot.branch%

```

**SplitPHP** will be checking for the configuration file `splitsh.json` in the current working directory by default. You can specify a different path by using the `-c` option:

```
bin/splitphp -c my/path/to/splitconfiguration.json

```

###  Health Score

29

—

LowBetter than 57% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity17

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity61

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~56 days

Total

4

Last Release

2895d ago

Major Versions

v1.0.0 → v2.0.02018-05-08

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/755057?v=4)[Tim Bureck](/maintainers/tbureck)[@tbureck](https://github.com/tbureck)

---

Top Contributors

[![tbureck](https://avatars.githubusercontent.com/u/755057?v=4)](https://github.com/tbureck "tbureck (14 commits)")

### Embed Badge

![Health badge](/badges/tbureck-splitphp/health.svg)

```
[![Health](https://phpackages.com/badges/tbureck-splitphp/health.svg)](https://phpackages.com/packages/tbureck-splitphp)
```

###  Alternatives

[matomo/matomo

Matomo is the leading Free/Libre open analytics platform

21.7k38.9k](/packages/matomo-matomo)[aeliot/todo-registrar

Register TODOs from source code in issue tracker

153.0k](/packages/aeliot-todo-registrar)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)