Interval Pull Requester with bundler/carton/david/cocoapods/composer/yarn/ncu/none update.
Clone or download
Latest commit ec251e6 Jun 22, 2017
Failed to load latest commit information.
bin Move command to thor class Dec 19, 2013
data Write a document for the pull_request_title Jun 3, 2017
lib Make pull request title changeable Jun 3, 2017
spec add Yarn Mar 21, 2017
.gitignore Ignore bundler binstubs Dec 18, 2014
.hound.yml Use rubocop setting Oct 31, 2014
.rspec Exec rspec --init Jul 2, 2013
.rubocop.yml chore(rubocop): override houndci settings Jan 25, 2015
.travis.yml Update travis rubies Jan 8, 2017 docs(changelog): build Mar 29, 2017
Gemfile ♻️ Remove json and oj gem Jan 8, 2017
LICENSE.txt Initial commit Jun 20, 2013
NOTE.txt Remove done todo Jul 2, 2013 docs(readme): add strategies Mar 29, 2017
Rakefile Add space after sharp Aug 19, 2013
tachikoma.gemspec ♻️ Remove json and oj gem Jan 8, 2017


Gem Version Build Status Code Climate Coverage Status

Tachikoma is a Interval Pull Requester with bundler/carton/david/yarn/npm-check-updates/cocoapods/carthage/composer/none update. This is Actual pull request.

tachikoma tachikoma

Most aspects of its behavior can be tweaked via various configuration options.


You can use these strategies:

  • Bundler (Ruby)
  • Carton (Perl)
  • David (Node.js)
  • Yarn (Node.js)
  • npm-check-updates (Node.js)
  • CocoaPods (Objective-C, Swift)
  • Carthage (Swift)
  • Composer (PHP)
  • None (without strategy)

If you use carton, then you use tachikoma:run_carton instead of tachikoma:run_bundler. You can also use tachikoma:run_none, tachikoma:run_cocoapods, tachikoma:run_composer and tachikoma:run_david.


See configuration options.

Use as rubygem


$ mkdir -p my-tachikoma
$ cd my-tachikoma
$ bundle init
$ echo "gem 'tachikoma'" >> Gemfile
$ bundle
$ bundle exec tachikoma init

Write repository information

  1. Get GitHub OAuth2 token: See Creating an OAuth token for command-line use
  2. Add YAML of repository you want to build by Tachikoma: Copy data/bot-motoko-tachikoma.yaml then edit url and type. to clone URL of your repository. Change type to shared, if you use shared repository model.
  3. Run below command in your shell:
$ export BUILD_FOR=<your-repository-name-that-is-same-to-yaml-filename>
$ export TOKEN_YOUR_REPOSITORY_NAME_THAT_IS_SAME_TO_YAML_FILENAME=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
$ bundle exec rake tachikoma:run_bundler


gist-mail setting (data/gist-mail.yaml)


This is the result.

Build script example


Tachikoma will be maintained under the Semantic Versioning guidelines as much as possible. Releases will be numbered with the following format:


And constructed with the following guidelines:

  • Breaking backward compatibility bumps the major (and resets the minor and patch)
  • New additions without breaking backward compatibility bumps the minor (and resets the patch)
  • Bug fixes and misc changes bumps the patch

For more information on SemVer, please visit


  1. Fork it
  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 new Pull Request




  • Tachikoma 10min (Below v3.1 - Old API) Silent screen shot 2013-07-22 at 8 09 29 am



Web Service