Tool for adding GitHub release assets
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin
lib
spec
.circle-ruby
.gitignore
.prospectus
.rspec
.rubocop.yml
.travis.yml
CHANGELOG.md
Gemfile
LICENSE
README.md
Rakefile
targit.gemspec

README.md

targit

Gem Version Build Status Coverage Status Code Quality MIT Licensed

Manages GitHub release assets for pushing binaries and other large files

Usage

To upload a file as a release asset:

targit USER/REPO TAG /path/to/file

That will add the given file as a release asset for "TAG" on the given GitHub repo. If you haven't already stored GitHub credentials, it will prompt you for them.

To create a release that doesn't already exist, add -c:

targit -c dock0/arch v0.1.75 ./new_tarball.tar.gz

Specify a name for the release, if desired:

targit -c -r "cool release" dock0/arch v0.1.75 ./new_tarball.tar.gz

Adding -f will replace an existing release/asset, if they exist:

targit -f -c dock0/arch v0.1.75 ./newer_tarball.tar.gz

Use -n NAME to set the name for the asset (it defaults to the file's name):

targit -n special.tar.gz -f -c dock0/arch v0.1.76 ./custom_tarball.tar.gz

Content can also be provided via stdin:

echo "secrit data" | targit -f -c -n foobar dock0/arch v0.0.test

The release can be created as a prerelease via -p.

Using -a lets you use an alternate GitHub credential file, other than the default of ~/.octoauth.yml.

Installation

gem install targit

Contributors

  • Jon Chen for suggesting release assets for storing large files, and for coming up with the workflow that this gem is built to streamline.

License

targit is released under the MIT License. See the bundled LICENSE file for details.