pages-gem: "No GitHub API authentication" error

Fixed my issue (not saying it is yours) by adding…

github: [metadata]

…to _config.yml

@asnowfix solution didn’t work for me.

I ended up generating a token and putting it in my env:

Generate token: https://github.com/settings/tokens

Run:

JEKYLL_GITHUB_TOKEN=<your token> jekyll serve

Or you can add to your shell config file:

#  .zshrc, .bashrc or .bash_profile

export JEKYLL_GITHUB_TOKEN=<your token>

Then in terminal:

source ~/.zshrc

A ton thanks to @asnowfix The fix works very well.

I need to point out, add the code as it is. [metadata] will be automatically pulled by the generator.

@parkr I think the issue here is that it appears to break Jekyll’s watch functionality.

In the scenario described here, which I’m also hitting, I have the following:

Repro

• Setup the gemfile as described above
• run bundle exec jekyll serve (which watches for changes and regenerates each time)
• make a change to a file and save
• See the “warning” errors

Expected behavior

The files are still generated on each change and we can ignore the errors.

Actual behavior

The jekyll pipeline is broken. The file changes are not actually processed, because jekyll perceives an error to have happened during generation.

In addition to the warning message, I see the following errors:

Error: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
             Error: Run jekyll build --trace for more information.

Instead, we are required to force-quit jekyll and run bundle exec jekyll serve each time.

Does this help clarify the issue? If so, it would be awesome to open this up for a second look.

It’s also possible that this may be a separate issue entirely; if so, I’m happy to create a new ticket.

Update: A workaround (sort of?)

The workaround described here and referenced above requires two environment variables, a cacert file download, and seemingly a restart of the PC.

I’ll try this as a workaround and note it in my README if it works.

Alternatively, is there a way we can disable this gem or functionality locally? I apologize for jumping in with a lack of familiarity on the structure of the project (a project which I appreciate on a daily basis, btw – thank you!)

Hey @tomjohnson1492! This is expected. 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. 👍

For me, the simple solution was to create a personal access token (I only checked the public_repo scope as the repository is public), add it to an .env file in the repository like this:

JEKYLL_GITHUB_TOKEN=<personal access token>

And then added the dotenv gem to my Gemfile as such:

gem "dotenv"

After a bundle install, Jekyll now serves the site warning free with JEKYLL_GITHUB_TOKEN all set.

I have the same problem with the new version of github-pages (136) on jekyll (= 3.4.3). It breaks the common dev flow locally, that is the convenient edit-and-refresh way. So I hope it will be fixed soon.