Skip to content
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

404 Error from Github private repo #126

Open
dlamon1 opened this issue Aug 13, 2021 · 8 comments
Open

404 Error from Github private repo #126

dlamon1 opened this issue Aug 13, 2021 · 8 comments

Comments

@dlamon1
Copy link

dlamon1 commented Aug 13, 2021

I get a 404 error from Github when using a private repo. Am I missing something? The install form asked for my username and repository, it did not ask for a key or token. I have awarded my Vercel account permission to access the Github repo, this did not change the 404 error.

Looking through the Hazel repository, I cannot find where my specific username and repository are declared. Are these variables stored in Vercel? Also, are these variables something I could hardcode in the /lib/server.js file?

@dlamon1
Copy link
Author

dlamon1 commented Aug 13, 2021

Always, and I cannot stress this enough, read the documentation! Set the env variable TOKEN for private repos. As states in the Readme

@tarikhaiga
Copy link

@dlamon1 I can't figure out how to set a TOKEN for my private repo. Where should I add this in my files? or is this run via a CLI command?

Any examples would be great!

@ryandunnewold
Copy link

ryandunnewold commented Sep 24, 2021

@tarikhaiga

This is added inside of Vercel once you've deployed Hazel (https://vercel.com/ACCOUNT_NAME/PROJECT_NAME/settings/environment-variables)

Screen Shot 2021-09-24 at 11 10 20 AM

l

@tarikhaiga
Copy link

Thanks @ryandunnewold ! I added both TOKEN and GH_TOKEN in the Environment Variables section on Vercel but it still does not trigger an update when one is available.

How did you manage to make auto-updating work for private repos?

@ryandunnewold
Copy link

@tarikhaiga here was the issue I ran into (included my fix in there) #131

@Deliaz
Copy link

Deliaz commented Oct 1, 2021

I had to redeploy the app to make it read TOKEN variable

@dsegovia90
Copy link

Thanks @Deliaz, redeploying worked for me 👍🏻

@rzfzr
Copy link

rzfzr commented Jun 7, 2022

What's the leanest scope the token can have?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants