-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[github-auth] accept API token instead of user/pass #5
Comments
@bcomnes do you think https://github.com/rvagg/ghauth will do the trick? might also mean gh-release wouldn't need to rely on the |
Passwords are stored in ~/.config/gh-release.json Closes ungoldman#5
Passwords are stored in ~/.config/gh-release.json Closes ungoldman#5
Bret-MBR:gh-release-test bret$ gh-release
{ tag_name: 'v1.0.1',
target_commitish: '40c8e8708a315a00b7673eabbc27a83438305c10',
name: 'v1.0.1',
body: '* Made another release\n\n',
owner: 'bcomnes',
repo: 'gh-release-test',
draft: false,
prerelease: false }
? does this look right? Yes
{ [Error: {"message":"Server Error","documentation_url":"https://developer.github.com/v3"}]
message: '{"message":"Server Error","documentation_url":"https://developer.github.com/v3"}',
code: 500 } Woops forgot to push! |
Looks ready to merge to master to me if your cool with that. |
@bcomnes I'm still doing a little work on |
@bcomnes I ran into the 500 error from github too when forgetting to push for https://github.com/bcomnes/gh-release-test -- note to self to check if the commit being released is on github first then display a better error message. |
No description provided.
The text was updated successfully, but these errors were encountered: