Results for check-git-branch

CLI for displaying and interacting with recently checked-out git branches

Add checking local git branch before all Capistrano tasks

`gnav` is an simple command line tool for interactively checking out a git tag or branch.

Display PR and JIRA tickets info about the branches that are currently checked out on your git repository.

git-trac takes the repetition out of working with trac and git-svn. Easily download a patch, apply it at the right point in time, turn it into a commit with useful metadata, and check it out into a branch, all in one command. Created for (but not limited to) work on the Ruby on Rails core.

This is a Git branch selection tool. It provides a way to quickly look back at your most recently checked-out branches. You can list the branches, use the selector tool to add the branch name to your clipboard, or checkout to the selected branch.

# Rebase Migrations Rebase Migrations is a library and command line tool to rebase Rails migrations to have the latest timestamp. ## Installation ```console $ bundle add rails-rebase-migrations --group=development,test ``` ## Scenario Two team members, Alice and Bob, are working on the same Rails project and both are adding new database migrations. Alice realizes her migration depends on Bob's, but the migration timestamps are out of order. The `rebase-migration` command line tool can be used to reorder Alice's new migrations to have the latest timestamp in the sequence. ## Usage To rebase all new migrations with respect to the `main` git branch: ```console $ bundle exec rebase-migrations ``` To rebase all new migrations with respect to a different branch: ```console $ bundle exec rebase-migrations my-branch ``` The command has a `--check` argument that is useful for CI. To check that all new migrations are the latest in the sequence: ```console $ bundle exec rebase-migrations --check ``` It will exit with status code 1 if the check fails. The `--check` form also accepts a branch argument. ### Skipping Migrations To skip a specific migration files from the `--check` include `_skip_rebase` in its filename.

Caperoma automates many decisions related to the programming that you often don't realize, and which you can forget hundreds of times during the time of working on the project: pulling the latest code from upstream before you start working, remembering from which branch you started the feature to later make a pull request into it, creating & starting tasks in Jira, creating & starting tasks in Pivotal, naming branches, adding Jira ID into the branch name, style guide checks, commits, naming commits, adding Jira ID into commit name, adding Pivotal ID into commit name, git pushes, pull requests into correct branches, stopping tasks in Jira, stopping tasks in Pivotal, tracking time, logging time to Jira, switching back into the original branch and much more.

Check if wa are in production. It uses several metrics: - Does a $RAILS_ENV environment variable exist? Does it say 'production'? - Does a $RACK_ENV environment variable exist? Does it say 'production'? - Failing the above, are we on the Git "master" branch?

# Mod10 A simple gem to generate mod_10 check digits and check if integers are mod10 valid. ## Installation Add this line to your application's Gemfile: ```ruby gem 'mod_10' ``` And then execute: $ bundle Or install it yourself as: $ gem install mod_10 ## Usage Include the Mod10 module to make the following two methods available - generate_check_digit(value) Which returns an integer value for the mod10 check digit of a string or integer. Note: If the value is 0, then the argument was already mod10 valid. - is_mod10?(value) Returns true or false for the tested value is it is or isn't mod10 valid. ## Contributing 1. Fork it ( https://github.com/[my-github-username]/mod_10/fork ) 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create a new Pull Request

# Rack::ReadOnly This gem allows Rack based APIs to be set to read only. At the most basic it can be used like this from your `config.ru`: ```ruby require 'rack/read_only' use Rack::ReadOnly, { active: ENV["READ_ONLY"] == "1", response_body: '{ "error": "This API is currently in read only mode." }' } run MyApp ``` When in read only mode the API will continue to respond to GET, HEAD, and OPTIONS requests as normal, but reject POST, PUT, DELETE, and PATCH requests with the body specified, and a 503 error code. ## Installation Add this line to your application's Gemfile: ```ruby gem 'rack-read_only' ``` And then execute: $ bundle Or install it yourself as: $ gem install rack-read_only ## Development After checking out the repo, run `bin/setup` to install dependencies. To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release` to create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org). ## Contributing 1. Fork it ( https://github.com/jellybob/rack-read_only/fork ) 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Add some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create a new Pull Request Any new builds should pass the tests on [Travis](https://travis-ci.org/jellybob/rack-read_only)

= 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.