Skip to content

Latest commit

 

History

History
137 lines (101 loc) · 5.23 KB

README.md

File metadata and controls

137 lines (101 loc) · 5.23 KB
Raw

Tachikoma

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.

Strategies

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.

Setting

See configuration options.

Use as rubygem

see: https://github.com/sanemat/bot-motoko-tachikoma

$ 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

Example

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

url:
  'https://github.com/sanemat/gist-mail.git'
type:
  'fork'
pull_request_body:
  ':ideograph_advantage::ideograph_advantage::ideograph_advantage:'

This is the result.

Build script example

Versioning

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

<major>.<minor>.<patch>

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 http://semver.org.

Contributing

  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

Resources

Concept

Screencast

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

Talk

Article

Web Service