Skip to content

Commit 0d27124

Browse files
committed
doc some more
1 parent 9516c77 commit 0d27124

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

README.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@ Create a release for a node package on github.
44

55
[![](https://nodei.co/npm/gh-release.png)](https://www.npmjs.com/package/gh-release)
66

7+
Uses the [Github Releases API](https://developer.github.com/v3/repos/releases/) to create a new release using information from your `package.json` and `CHANGELOG.md`. Has strong defaults, relies on standards.
8+
79
## Usage
810

911
### Node
@@ -18,7 +20,7 @@ var options = {
1820
tag_name: 'v1.0.0',
1921
target_commitish: 'master',
2022
name: 'v1.0.0',
21-
body: '* create working prototype\n* define basic node interface\n* define basic cli interface\n',
23+
body: '* init\n',
2224
draft: false,
2325
prerelease: false,
2426
repo: 'gh-release',
@@ -35,6 +37,10 @@ ghRelease(options, auth, function (err, result) {
3537
})
3638
```
3739

40+
All settings in `options` are optional (see [options](#options) for defaults).
41+
42+
`username` and `password` in `auth` are required. Ideally this will support a token in the future as well -- storing these things in plaintext as env vars or anything else is obviously a bad idea. Right now user & pass are mainly there to support the CLI prompt use case.
43+
3844
### CLI
3945

4046
Should be run at the root of the project to be released.
@@ -80,10 +86,6 @@ Override defaults with flags ([cli](#cli)) or the `options` object ([node](#node
8086

8187
All [releases](https://github.com/ngoldman/gh-release/releases) of `gh-release` were created with `gh-release`.
8288

83-
## Reference
84-
85-
* [github release api docs](https://developer.github.com/v3/repos/releases/)
86-
8789
## Motivation
8890

8991
There are packages that already do something like this, and they're great, but I want something that does this one thing really well and nothing else, leans heavily on standards in `package.json` and `CHANGELOG.md`, and can work both as a cli tool and programmatically in node. Mostly I want this to work well as a dependency in [versioneer](https://github.com/ngoldman/versioneer).

0 commit comments

Comments
 (0)