From 21fcdd0ad0cb6be92043b0a4b01c58b9a69c0b8e Mon Sep 17 00:00:00 2001 From: Andrew Reed Date: Fri, 14 Jul 2017 15:24:03 -0700 Subject: [PATCH] typos and homebrew homepage points to docs [ch568] --- .goreleaser.yml | 2 +- README.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.goreleaser.yml b/.goreleaser.yml index 01525e936..f4e5bb28a 100644 --- a/.goreleaser.yml +++ b/.goreleaser.yml @@ -9,7 +9,7 @@ brew: name: homebrew-replicated folder: HomebrewFormula install: bin.install "replicated" - homepage: https://replicated.com + homepage: https://www.replicated.com/docs/reference/vendor-cli/ description: "Manage your app's channels and releases from the command line" builds: - goos: diff --git a/README.md b/README.md index 1de11ed37..5cb44a07a 100644 --- a/README.md +++ b/README.md @@ -33,9 +33,9 @@ replicated channel ls ### CI Example Creating a new release for every tagged build is a common use of the replicated command. -Assume the app's yaml config is checked in at replicated.yaml and you have configured TravisCI or CircleCI with your REPLICATED_APP_SLUG and REPLICATED_API_TOKEN environment variables, as well as UNSTABLE_CHANNEL_ID```. +Assume the app's yaml config is checked in at replicated.yaml and you have configured TravisCI or CircleCI with your REPLICATED_APP_SLUG and REPLICATED_API_TOKEN environment variables. -Then add a release.sh script to your project looking something like this: +Then add a release.sh script to your project something like this: ```bash #!/bin/bash @@ -138,5 +138,5 @@ The models are generated from the API's swagger spec. ### Releases Releases are created on Travis when a tag is pushed. This will also update the docs container. ``` -git tag -a v0.1.0 -m "First release" && git push origin v0.1.0 +git tag -a v0.1.0 -m "First release" && git push upstream v0.1.0 ```