Results for isolate-git

Git plugin for Isolate.

Shell-agnostic tool for managing Rails git worktrees with separate databases, unique ports for Rails and Vite, and isolated environments

ace-git-worktree creates isolated worktrees for tasks, pull requests, and branches, with task metadata updates, configurable hooks, and cleanup workflows for focused development.

Easily create, initialize, and close git worktrees with isolated databases and configurations for Rails projects

Creates isolated database copies for each git branch, enabling parallel feature development without schema conflicts.

A Rails database adapter that gives each git branch its own Postgres schema. Migrations run in isolation. Nobody steps on anyone else's work.

ruby-skill-bench orchestrates evaluation runs of AI coding agents inside isolated git sandboxes, then scores the results using deterministic and LLM-powered judges.

tddium runs your rspec, cucumber, and test::unit tests in our managed cloud environment. You can run tests by hand, or enable our hosted CI to watch your git repos automatically. Tests run in parallel to save you time, and, if you use Rails, tddium takes care of setting up fresh isolated DB instances for each test instance. Tests can access a limited set of private Selenium RC servers.

Carson is an autonomous git strategist and repositories governor that lives outside the repositories it governs — no Carson-owned artefacts in your repo. As strategist, Carson knows when to branch, how to isolate concurrent work, and how to recover from failures. As governor, it enforces review gates, manages templates, and triages every open PR across your portfolio: merge what's ready, dispatch coding agents to fix what's failing, escalate what needs human judgement. One command, all your projects, unmanned.

Solano CI runs your test suite simply and quickly in our managed cloud environment. You can run tests by hand, or enable our hosted CI to watch your git repos automatically. Solano CI automatically and safely parallelizes your tests to save you time, and takes care of setting up fresh isolated DB instances for each test thread. Tests have access to a wide variety of databases (postgres, mongo, redis, mysql, memcache), solr, sphinx, selenium/webdriver browsers, webkit and culerity. Solano CI supports all common Ruby test frameworks, including rspec, cucumber, test::unit, and spinach. Solano CI also supports Javascript testing using jasmine, evergreen, and many other frameworks.

Predix CI runs your test suite simply and quickly in our managed cloud environment. You can run tests by hand, or enable our hosted CI to watch your git repos automatically. Predix CI automatically and safely parallelizes your tests to save you time, and takes care of setting up fresh isolated DB instances for each test thread. Tests have access to a wide variety of databases (postgres, mongo, redis, mysql, memcache), solr, sphinx, selenium/webdriver browsers, webkit and culerity. Predix CI supports all common Ruby test frameworks, including rspec, cucumber, test::unit, and spinach. Predix CI also supports Javascript testing using jasmine, evergreen, and many other frameworks.

= epubforge = Write your book in markdown, then do all sorts of increasingly nifty things with it using this command-line utility. == Project description == epubforge is a command-line utility for creating, tracking and managing longer (novella and book-length) writing projects. Write your text in markdown (http://whatismarkdown.com/), use the built in actions to convert your project to various ebook formats, track wordcount over the life of the project, manage a story bible, and back your project up using git. Or go further and define your own formatters/converters and actions in Ruby. Have fun! == Contributing to epubforge == * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet. * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it. * Fork the project. * Start a feature/bugfix branch. * Commit and push until you are happy with your contribution. * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally. * Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it. == Copyright == Copyright (c) 2013 Bryce Anderson. See LICENSE.txt for further details.

No description provided.

No description provided.

No description provided.