README.md in circleci-bundle-update-pr-1.6.0 vs README.md in circleci-bundle-update-pr-1.6.1
- old
+ new
@@ -1,7 +1,15 @@
-# Circleci::Bundle::Update::Pr [![Gem Version][gem-badge]][gem-link]
+# Circleci::Bundle::Update::Pr
+[![Build Status](https://img.shields.io/circleci/project/masutaka/circleci-bundle-update-pr/master.svg?style=flat-square)][circleci]
+[![License](https://img.shields.io/github/license/masutaka/circleci-bundle-update-pr.svg?style=flat-square)][license]
+[![Gem](https://img.shields.io/gem/v/circleci-bundle-update-pr.svg?style=flat-square)][gem-link]
+
+[circleci]: https://circleci.com/gh/masutaka/circleci-bundle-update-pr
+[license]: https://github.com/masutaka/circleci-bundle-update-pr/blob/master/LICENSE.txt
+[gem-link]: http://badge.fury.io/rb/circleci-bundle-update-pr
+
circleci-bundle-update-pr is an automation script for continuous bundle update and for sending a pull request via CircleCI [Nightly builds](https://circleci.com/docs/nightly-builds/).
By requesting a nightly build to CircleCI with an environment variable configured in `circle.yml` to execute this script, bundle update is invoked, then commit changes and send a pull request to GitHub repository if there some changes exist.
## Installation
@@ -71,12 +79,12 @@
```
NOTE: Please do not forget to replace `<username>/<reponame>/<circleci api token>` with yours.
-### Trigger nightly build via ci-bundle-update (recommended)
+### Trigger nightly build via ci-build-trigger (recommended)
-While you can trigger nightly builds by using whatever you want for sending requests to API, the most recommended way is to use "ci-bundle-update". Please see https://github.com/masutaka/ci-bundle-update for details.
+While you can trigger nightly builds by using whatever you want for sending requests to API, the most recommended way is to use "ci-build-trigger". Please see https://github.com/masutaka/ci-build-trigger for details.
## CLI command references
General usage: