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

Error on GitHub Pages deploy step (w/ GitHub Organizations) #61

Closed
querkmachine opened this issue Nov 18, 2020 · 6 comments
Closed

Error on GitHub Pages deploy step (w/ GitHub Organizations) #61

querkmachine opened this issue Nov 18, 2020 · 6 comments
Labels
question Further information is requested

Comments

@querkmachine
Copy link

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.

error: src refspec ***@github.com/severnbronies/status.git does not match any
error: failed to push some refs to 'https://'

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!

@pavelloz
Copy link

pavelloz commented Nov 19, 2020

I had identical error message today, reinitializing everything in a new repo fixed it for me :)

#59 (comment)

Try using template -> Add secret with rights -> Push to GH -> Let workflows do their thing, set up static pages -> Then apply your changes

@pavelloz
Copy link

Anyway i think you need to remove CNAME from gh-pages branch to not use default upptime domain :)
severnbronies/status@44212a6#diff-76b26edb75578663ca0fd6515ec7880ca04046bdbab298938981c9f0bd3907dd

If i were you, i would just remove everything from that branch - upptime will populate it anyway. Good luck!

@AnandChowdhary
Copy link
Member

This looks very similar to #59, hmm. I'll have a closer look!

@querkmachine
Copy link
Author

querkmachine commented Nov 19, 2020

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?

@AnandChowdhary
Copy link
Member

That's right, this is only updated once (this is by design, so user changes are not overwritten). 😄

@AnandChowdhary AnandChowdhary added the question Further information is requested label Nov 19, 2020
@querkmachine
Copy link
Author

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!

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

No branches or pull requests

3 participants