-
Notifications
You must be signed in to change notification settings - Fork 887
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
Error on GitHub Pages deploy step (w/ GitHub Organizations) #61
Comments
I had identical error message today, reinitializing everything in a new repo fixed it for me :) Try using template -> Add secret with rights -> Push to GH -> Let workflows do their thing, set up static pages -> Then apply your changes |
Anyway i think you need to remove CNAME from gh-pages branch to not use default upptime domain :) If i were you, i would just remove everything from that branch - upptime will populate it anyway. Good luck! |
This looks very similar to #59, hmm. I'll have a closer look! |
Reinitialising the repo and letting it run through with the default config before changing it, as @pavelloz suggested, seems to have resolved the deployment issue. A minor problem with doing it that way is that re-running the Setup CI after updating the configuration doesn't update the names and links in the README or repo metadata, which still use the default ones. Presumably these aspects of the file aren't overwritten once they're in place? |
That's right, this is only updated once (this is by design, so user changes are not overwritten). 😄 |
Makes sense! This weird thing of having to let the unmodified template set up and generate all of the stuff that then needs to be manually changed later is probably something to look into. Thanks for the help, folks! |
Ahoy,
I'm setting this up for a GitHub Organization, the repo for which is here. For some reason, the GitHub Pages Deploy step always produces this error, regardless of which action is performing it.
Is there some extra setup needed to get Upptime working with GitHub Organizations? Given orgs do not have Personal Access Tokens, I've used one generated on my personal account instead.
I've tried re-doing set up a few times with the same result, and my configuration isn't drastically different from the default (which is for an org), so I'm at a bit of a loss. Your help appreciated! Thanks!
The text was updated successfully, but these errors were encountered: