-
Notifications
You must be signed in to change notification settings - Fork 114
Can't use release for private repository #139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @praveenpuglia. Have you solved this problem? I am looking for a tool like this, but I would like to know if it will work for me. I am also working on a private repository. |
@joaolavoier-luizalabs nope. It still doesn't work for private repositories. I don't know if release needs a special github token to work with private repositories. Haven't got any help from any team member here too. So no idea. |
I see! I think this is the same issue. #130 |
Is this still an issue? It seems to work fine ...for me... Have you tried with more than one repo? |
I faced this with the latest release that's 4.0.2 from 9th August. |
I randomly found out the solution just last week. In my case I migrated my repo into an org, which means the |
I see why this is going to work but is it safe to give it the private access because this seems scary!
|
Yeah wish there was a better solution to this |
Hi!
I have used release before and it works perfectly fine for public repositories. But for private repositories I always face the following.
Here's what the package.json looks like.
I am not sure why this error comes up -
Error! Could not determine GitHub repository
. Does release need some Auth token from github in order to work for private repos?The text was updated successfully, but these errors were encountered: