Results for patch-commits

A script to rewrite git patches/commits, while keeping commits history

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.

CLI tool to create version bump commit and tag with newest version in a Git repository. Versioning is based on [Semantic Versioning](http://semver.org/). Version bump types include MAJOR, MINOR, and PATCH. Once installed gem can be used in a Git repository by running `versionify bump TYPE`

This tool 1. create's a new branch 2. runs 'bundle update' 3. find's the latest patch-level version of Ruby and updates files that reference the version 4a. commit's the updates and pushes to gitlab, creating a new merge request 4b. delete's the branch if no updates were made

= Ungulate According to Wikipedia, this can mean "hoofed animal". Camels have hooves. This is a gem for uploading and processing images using an Amazon Web Services stack. It comes with a few goodies: * ungulate_server.rb - simple queue runner that expects a YAML-encoded job description for RMagick * Ungulate::FileUpload - a model for e.g. Rails that does some cryptography stuff - example to follow * A view helper for Rails: "ungulate_upload_form_for" == Installation gem install ungulate == Documentation http://wiki.github.com/camelpunch/ungulate/ == 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) 2011 Camel Punch Limited. See LICENSE for details.

What is send? ============= It’s a tiny wee ruby gem that is a fork of [Object#try](http://ozmm.org/posts/try.html) and [Object#try from Rails](http://api.rubyonrails.org/classes/Object.html#M000027). It will *never* throw a NoMethodError (no matter the receiver), and returns nil if called on a nil-class or if the method in the receiver does not exist. Note on Patches/Pull Requests ----------------------------- 1. [Fork me!](http://github.com/Burgestrand/send-/fork) 2. Write tests for your new feature or bug fix (important, I don’t want to break your stuff in a future update by accident!) 3. Hack away on the code; make your tests pass. 4. Commit! Don’t touch Rakefile, version or git history in any of the commits you want me to pick. 5. ??? 6. Send me a pull request!

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

# 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)

= sinatra-mongo Extends Sinatra with an extension method for dealing with monogodb using the ruby driver. Install it with gem: $ gem install sinatra-mongo Now we can use it an example application. require 'sinatra' require 'sinatra/mongo' # Specify the database to use. Defaults to mongo://localhost:27017/default, # so you will almost definitely want to change this. # # Alternatively, you can specify the MONGO_URL as an environment variable set :mongo, 'mongo://localhost:27017/sinatra-mongo-example' # At this point, you can access the Mongo::Database object using the 'mongo' helper: puts mongo["testCollection"].insert {"name" => "MongoDB", "type" => "database", "count" => 1, "info" => {"x" => 203, "y" => '102'}} get '/' do mongo["testCollection"].find_one end If you need to use authentication, you can specify this in the mongo uri: set :mongo, 'mongo://myuser:mypass@localhost:27017/sinatra-mongo-example' == Mongo Reference * http://www.mongodb.org/display/DOCS/Ruby+Tutorial == 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 Joshua Nichols. See LICENSE for details.

= sinatra-mongo Extends Sinatra with an extension method for dealing with monogodb using the ruby driver. Install it with gem: $ gem install sinatra-mongo Now we can use it an example application. require 'sinatra' require 'sinatra/mongo' # Specify the database to use. Defaults to mongo://localhost:27017/default, # so you will almost definitely want to change this. # # Alternatively, you can specify the MONGO_URL as an environment variable set :mongo, 'mongo://localhost:27017/sinatra-mongo-example' # At this point, you can access the Mongo::Database object using the 'mongo' helper: puts mongo["testCollection"].insert {"name" => "MongoDB", "type" => "database", "count" => 1, "info" => {"x" => 203, "y" => '102'}} get '/' do mongo["testCollection"].find_one end If you need to use authentication, you can specify this in the mongo uri: set :mongo, 'mongo://myuser:mypass@localhost:27017/sinatra-mongo-example' == Mongo Reference * http://www.mongodb.org/display/DOCS/Ruby+Tutorial == 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 Joshua Nichols. See LICENSE for details.

- xcsims: Delete all simulators and recreate one for each compatible platform and device type pairing. - sync-git-remotes: Make sure all your GitHub repos are cloned into a given directory and keep them synced with upstream. Forks are maintained with a remote for both the fork and upstream, both remotes' default branches are tracked in local counterparts, and the upstream default branch is also pushed to the fork. - changetag: Extract changelog entries to write into git tag annotation messages. - prerelease-podspec: Branch and create/push a release candidate tag, modify the podspec to use that version tag, and try linting it. - release-podspec: Create a tag with the version and push it to repo origin, push podspec to CocoaPods trunk. - revert-failed-release-tag: In case `release-podspec` fails, make sure the tag it may have created/pushed is destroyed before trying to run it again after fixing, so it doesn't break due to the tag already existing the second time around. - bumpr: Increment the desired part of a version number (major/minor/patch/build) and write the change to a git commit. - clean-rc-tags: deletes any release candidate tags leftover after prerelease testing. - migrate-changelog: for a changelog adhering to [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), move any contents under Unreleased to a new section for a new version with the current date.

==== subj3ct - The DNS for the Semantic Web This is a Ruby adapter for the subj3ct.com webservice. Subj3ct is an infrastructure technology for Web 3.0 applications. These are applications that are organised around subjects and semantics rather than documents and links. Subj3ct provides the technology and services to enable Web 3.0 applications to define and exchange subject definitions. Or in other words: Subj3ct.com is for the Semantic Web what DNS is for the internet. ==== Installing Install the gem: gem install subj3ct ==== Usage Query a specific subject - to be specific: its subject identity record - using it's identifier: Subj3ct.identifier("http://www.topicmapslab.de/publications/TMRA_2009_subj3ct_a_subject_identity_resolution_service") See the README or the github page for more examples. ==== Subj3ct vs. Subject The official name is "Subj3ct", however in this API, you can also use "Subject" which may be easier to remember or to type for normal, n0n-1337 people. It should work for the gem, for the require and for the main module. ==== Contribute! Subj3ct is a young and ambitious service. It's free, will stay free and needs your help. Contribute to this library! Create bindings for other languages! Publish your data as linked data to the web and register it with subj3ct.com. ==== Note on Patches/Pull Requests * Fork the project on http://github.bb/subj3ct * 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) 2010 Benjamin Bock, Topic Maps Lab. See LICENSE for details.

No description provided.