Fix rendering on forks #307
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bkeepers
force-pushed
the
render-forks
branch
from
6e138a1
to
540e145
Compare
|
There are still some things to fix on forks, but it's going to require some changes to upstream jekyll. I'm going to merge this and will work on that separately. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When you fork this repo and push a commit to the
gh-pagesbranch, it will get rendered onyourname.github.io/open-source-guide. This fixes it so the page renders properly on forks.I'd like to update the PR guidelines to ask people to include a link to their changes so we can preview them without having to build the site locally.