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

πŸ—οΈπŸ”§ add support for JEKYLL_GITHUB_TOKEN env var #612

Merged
merged 1 commit into from
Aug 26, 2022
Merged

πŸ—οΈπŸ”§ add support for JEKYLL_GITHUB_TOKEN env var #612

merged 1 commit into from
Aug 26, 2022

Conversation

DerekNonGeneric
Copy link
Member

The jekyll-github-metadata gem is automatically enabled for GitHub Pages builds (including builds using this gem locally). It pulls in information from the GitHub API, but first checks the environment for authentication, which is required for some API calls to return the data we want. It's a warning, not an error, so you should be good to ignore them locally. πŸ‘
β€” github/pages-gem#399 (comment)


"GitHub Metadata: No GitHub API authentication could be found. Some fields may be missing or have incorrect data."

To create a personal access token: (public_repo scope is enough for public repository): https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token

Refs: github/pages-gem#399

@DerekNonGeneric
Copy link
Member Author

I am going to land this momentarily, but if anyone gets stuck, here are the docs:

There is a followup PR to be made as it seems this should be documented (perhaps in the file being added by #611).

@DerekNonGeneric DerekNonGeneric merged commit df3dafc into OpenINF:live Aug 26, 2022
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

Successfully merging this pull request may close these issues.

1 participant