**Fault-tolerant state capture for distributed development.**
[](https://pypi.org/project/git-pulsar/)
[](https://github.com/JacksonFergusonDev/git-pulsar/actions/workflows/ci.yml)
[](https://github.com/JacksonFergusonDev/git-pulsar/actions/workflows/release.yml)
[](https://www.python.org/downloads/)
[](https://github.com/Textualize/rich)
[](https://github.com/pre-commit/pre-commit)
[](LICENSE)
**Standard `git commit` conflates two distinct actions: *saving your work* (frequency: high, noise: high) and *publishing a feature* (frequency: low, signal: high).**
**Git Pulsar decouples them. It is a background daemon that provides high-frequency, out-of-band state capture, ensuring your work is immutable and recoverable without polluting your project history.**
## 📡 The Mission: Decoupling Signal from Noise
In a typical workflow, developers are forced to make "WIP" commits just to switch machines or save their progress. This introduces **entropy** into the commit log, requiring complex interactive rebases to clean up later.
**Git Pulsar** treats the working directory state as a continuous stream of data. It captures this "noise" in a dedicated namespace (`refs/heads/wip/...`), keeping your primary branch purely focused on "signal" (logical units of work).