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

Allow GitHub Pages on forks #726

Open
deadmeu opened this issue May 3, 2024 · 2 comments
Open

Allow GitHub Pages on forks #726

deadmeu opened this issue May 3, 2024 · 2 comments

Comments

@deadmeu
Copy link
Contributor

deadmeu commented May 3, 2024

I'm trying to test a small change but am unable to do so due to #725.

I figured I could just have GitHub Pages host it for me to test with, and the project's README provides steps for doing so, but the option is unavailable to me in my fork due to a policy issue:
image

Is this something that can be relaxed, to allow GitHub Pages to work on forks?

@martinpitt
Copy link
Member

I wish I knew.. This is a mystery to me. The "upstream" https://github.com/cockpit-project/cockpit-project.github.io/settings/pages even has this:

image

Although that's blatantly bogus -- after all, https://cockpit-project.org/ is that very result from Pages..

A lot of people in our team also have forks -- e.g. https://github.com/martinpitt/cockpit-project.github.io is a fork which renders just fine to https://martinpitt.github.io/cockpit-project.github.io/blog/ . But my https://github.com/martinpitt/cockpit-project.github.io/settings/pages shows exactly the same error as your screenshot.

The fork is actually working for half of the people in our team, and not for the other half. I'm afraid so far we don't have the slightest idea what goes wrong.

@garrett
Copy link
Member

garrett commented May 14, 2024

As @martinpitt said, it's a mysterious bug that's not really accurate in GitHub's UI. Hopefully it'll work for you regardless of the message?

FWIW: I just fixed that odd gem dependency error that hit our container scripts. Those should work again. Apologies for the delay. (BTW: This is the first time that a bug like that hit our container build method that I'm aware of. Normally it's rock solid for local development and testing.)

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

3 participants