Get the current state of any git repository
TypeScript definitions for git-state
Local developer cockpit for projects, processes, logs, ports, Git state, and AI context.
Opinionated git state context injection for pi
Real-time status bar for Claude Code showing context usage, rate limits, and git state
Declarative companion to shell state mutations (cd, export, git checkout/switch). Emits structured JSON describing cwd, env, and git state.
Enter/exit a state
ECMAScript (ESTree) AST walker
Behavioral eval runner for AI coding agents — snapshot a workspace, hand it to a runner with a task prompt, score the resulting filesystem/git state.
Get the current state of any git repository
Zero-config MCP server that gives AI coding assistants a real-time diagnostic snapshot of your local dev environment — framework, running services, recent errors, git state, and health diagnosis in one call
Lint files staged by git
This is lightweight memory stream module for node.js.
This is an internal utility, not intended for public usage.
A collection of node utility functions which help to automate the the process of committing and pushing NPM packages with git, updating dependency versions in package.json files, and viewing the git state of local repos
Save window positions and sizes and restore them when the app is reopened.
Behavioral eval runner for AI coding agents — snapshot a workspace, hand it to a runner with a task prompt, score the resulting filesystem/git state.
Experimental sandboxed JS execution and filesystem runtime for Cloudflare Workers agents
Provides metadata and conversions from repository urls for GitHub, Bitbucket and GitLab
ProseMirror editor state
Core Inquirer prompt API
Editor state data structures for the CodeMirror code editor
Shared utilities for Paperclip adapters: process spawning, environment injection, sandbox/SSH transport, workspace sync, and the round-trip helpers that move code between the local execution-workspace cwd and wherever the agent actually runs.
Run a command if a file changes via Git hooks
Save your encypted terraform state in git.
Saves and restores the state of your local database as you work on different git branches.
git_test runs your tests and stores them in git. Use git_test to track tests over multiple branches, runs, and teammates. Run git_test when you pull and push and you'll always know the state of your project!
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.
This gem is a wrapper for Scott Chacon's ruby-git gem with commands that streamline the process of creating repositories in a given state. Its primary purpose is for demonstrating common Git scenarios, but it is handy for scripting basic repository operations.
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.
Git Cleaner allows you to easily remove stale branches based on a number of factors, such as date modified, branch name, and even Lighthouse ticket state.
Communicates with the beachcomber daemon over a Unix domain socket to query cached shell-environment data (git state, hostname, battery, etc.).
Some call it the unlimited undo. It tracks every single file change in a git repository. Hangover runs in the background. The file changes get committed to the next parent hangover repository. You can restore any state of your files from the moment on you started hangover.
Sirena is a pure Ruby implementation of Mermaid diagram rendering. It parses Mermaid syntax and generates SVG output using Parslet grammars and ELK layout. Supports 24 diagram types: flowcharts, sequence, class, state, ER, C4, block, architecture, Gantt, timeline, Git graph, mindmap, Kanban, user journey, pie, quadrant, radar, XY charts, requirement, Sankey, packet, treemap, info, and error displays.
= 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.
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.