You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Is this something that can be relaxed, to allow GitHub Pages to work on forks?
The text was updated successfully, but these errors were encountered:
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.
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.)
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:
Is this something that can be relaxed, to allow GitHub Pages to work on forks?
The text was updated successfully, but these errors were encountered: