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.

Sign up for GitHub

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

Jump to bottom

possibility to use private repo's #23

Closed
Haroenv opened this issue Jan 8, 2016 · 5 comments · May be fixed by #58
Closed

possibility to use private repo's #23

Haroenv opened this issue Jan 8, 2016 · 5 comments · May be fixed by #58
Labels
bug frozen-due-to-age stale

Comments

@Haroenv
Copy link

Haroenv commented Jan 8, 2016

This would be interesting for repo's that have a gh-pages branch, but are private, or for personal use.

This would use the visibility key present in the api.

https://developer.github.com/v3/repos/
@parkr
Copy link
Member

parkr commented Jan 8, 2016

I'm in! Would love to see a pull request when you have time.

@benbalter
Copy link
Contributor

To note, if the repo's private, we shouldn't cache it, if we do, via #7.

@parkr parkr added the bug label Jan 10, 2016
@Crunch09
Copy link
Member

Hi all,
just to clarify do you mean access to something like site.github.repositories instead of only site.github.public_repositories ?

@Haroenv
Copy link
Author

Haroenv commented May 10, 2016

Maybe .repositories and .private_repositories

Crunch09 added a commit to Crunch09/github-metadata that referenced this issue May 12, 2016
@Crunch09
Add site.github.private_repositories field
af1c819 
This creates a GET request to /user/repos with type set to `private`.
See https://developer.github.com/v3/repos/#list-your-repositories for more
information.

fixes jekyll#23
@Crunch09 Crunch09 mentioned this issue May 13, 2016
Open
@jekyllbot
Copy link
Contributor

This issue has been automatically marked as stale because it has not been commented on for at least
one month.

The resources of the Jekyll team are limited, and so we are asking for your help.

If you can still reproduce this error on the 3.1-stable or master branch,
please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, please consider building it first as a plugin. Jekyll 3 introduced
hooks which provide convenient access points throughout
the Jekyll build pipeline whereby most needs can be fulfilled. If this is something that cannot be
built as a plugin, then please provide more information about why in order to keep this issue open.

Thank you for all your contributions.

@jekyll jekyll locked and limited conversation to collaborators Apr 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug frozen-due-to-age stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add site.github.private_repositories field Crunch09/github-metadata
5 participants
@parkr @benbalter @Crunch09 @jekyllbot @Haroenv