x/urfave-cli
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Add another bit about pinning to v1

Browse Source
This commit is contained in:
Dan Buch 2016-05-16 10:46:43 -04:00
parent 1beb5f66cd
commit 8af550936f
No known key found for this signature in database
GPG Key ID: FAEF12936DD3E3EC
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -51,6 +51,24 @@ import (
... ...
``` ```
### Pinning to the `v1` branch
Similarly to the section above describing use of the `v2` branch, if one wants
to avoid any unexpected compatibility pains once `v2` becomes `master`, then
pinning to the `v1` branch is an acceptable option, e.g.:
```
$ go get gopkg.in/codegangsta/cli.v1
```
``` go
...
import (
"gopkg.in/codegangsta/cli.v1" // imports as package "cli"
)
...
```
## Getting Started ## Getting Started
One of the philosophies behind cli is that an API should be playful and full of discovery. So a cli app can be as little as one line of code in `main()`. One of the philosophies behind cli is that an API should be playful and full of discovery. So a cli app can be as little as one line of code in `main()`.