Git layer for pvm
blamer is a tool for getting information about author of code from version control system
Run Claude Code, Codex, Aider, Gemini CLI, and Cursor as isolated, reviewable attempts with repo-local memory, agent handoff, and apply/recover. MIT, no SaaS.
opinionated scaffolder for new projects
The GrowthBook command-line interface (CLI) for working with the GrowthBook A/B testing, feature flagging, and experimentation platform
OpenVCS Git plugin - Node.js runtime
Provides metadata and conversions from repository urls for GitHub, Bitbucket and GitLab
File operations class
OpenVCS SDK CLI for plugin scaffolding and runtime asset builds
Get raw git commits out of your repository using git-log(1).
Headless custom version control system for Mora projects
A Javascript library for generating and performing common operations on Linked Data cryptographic key pairs.
A lightweight daemon framework for building persistent background agents that communicate over WebSocket using JSON-RPC 2.0. Originally built for [C4A](../../README.md) (Context For AI) to bridge remote servers with local filesystems and Git repositories,
a util for spawning git from npm CLI contexts
Simple GIT interface for node.js
List of Git hooks
A high level git url parser for common git providers.
Get all git semver tags of your repository in reverse chronological order.
A library for getting data from Formant
A low level git url parser.
Compiles and stores base binaries for pkg
A video-oriented JavaScript graphics framework based on React, created by [Daily](https://daily.co).
Get the remote origin URL of a Git repository
Simple git client for conventional changelog packages.
Automate the Git CLI from Rust through process execution.
Language Server Protocol implementation for Debian control files with field completion, diagnostics, and quickfixes
Large scale VCS change management
Git import, export, and roundtrip plumbing for Claw VCS.
Automate the GitHub CLI (gh) from Rust through process execution.
Import VCS .repos as Git submodules
Simple shell for VCS(Version Controll System)s like svn, hg, git, etc.
A Ruby gem designed implementing a simple Git-like version control system on top of vcs-toolkit.
vcs-ann is an interactive wrapper for "annotate" and "diff" of svn and git. vcs-ann enables you to browse annotated sources and diffs interactively.
Allows easy to use platform for building a Version Control System. It's a proof-of-concept that VCS systems such as Git are simple in their implementation
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.
= rails_vcstatus_logger It adds current state of version control to the log when you start the server. * Currently only supports git Adds current version hash and result of `git diff` The idea is that you can be sure about what source was running when you look in the log. I recently had a situation where i wasn't sure when a change was put up on the live server. Please add support for your vc system and send me a pull request! Just add this to enivorment.rb config.gem 'bjornblomqvist-rails_vcstatus_logger', :lib => 'rails_vcstatus_logger', :source => 'http://gems.github.com' == Note on Patches/Pull Requests * Fork the project. * Make your feature addition or bug fix. * Add tests for it. This is important so I don't break it in a future version unintentionally. * Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull) * Send me a pull request. Bonus points for topic branches. == Copyright Copyright (c) 2009 Bjorn Blomqvist. See LICENSE for details.
Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.