-
Notifications
You must be signed in to change notification settings - Fork 135
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
Expose site source #107
Expose site source #107
Conversation
spec/webmock/api_get_repo_pages.json
Outdated
{"message":"Not Found","documentation_url":"https://developer.github.com/v3"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm this should have valid data :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't modify this. Restored the whitespace via 43e425b to clean up the diff.
Based on trying to implement things differently the first time, I believe this is here to ensure that repo compat is exercised for the integration test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah! Ok cool, looking through the history, it looks like it's trying to fetch data from this repo, which doesn't have Pages enabled so that'd explain it. Womp. Ideally we'd exercise both repo compat and the repo API stuff.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missed this at first glance. Added unit tests via 7abdfe2.
I love this!! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am suuuuuper stoked for this!
One enhancement we might consider is adding a Liquid tag like {%- github_edit_link page -%}
which would output an HTML <a>
link all built for you. The big reason not to do that is people will want lots of options like setting CSS tags and so forth. Maybe {%- github_edit_url page -%}
? 😄 Something to think about.
Thank you!!
@jekyllbot: merge +minor. |
...and one more PR to follow up on expose repo license and expose repo visibility.
The idea is still to enable a template as follows: