Before submitting an issue, please be sure to
This issue affects
What did you do (e.g., steps to reproduce)
Add this into the Gemfile:
What did you expect to happen?
I did not expect that Github Metadata error to appear.
When I removed the Gemfile, the error went away. Since this is the only gem outside of Jekyll that I'm using in my project, I suspect the error has something to do with github-pages. That's why I'm filing an issue here.
I fixed the issue by following the resolution described here. This removed the error from occurring.
I just wanted to report this error in case there's something with the github-pages gem that is causing it.
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.
@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:
The files are still generated on each change and we can ignore the errors.
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:
Instead, we are required to force-quit jekyll and run
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
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!)
The work-around described above does not work for me. I am using a GitHub Enterprise instance & tried using a personal access token generated by GHE & a one generated by GH.com. None worked & I am still getting the error message at each refresh:
Despite the hint above,
@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
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:
GitHub Metadata: Error processing value 'baseurl': ERROR: YOUR SITE COULD NOT BE BUILT: ------------------------------------ No repo name found. Specify using PAGES_REPO_NWO environment variables, 'repository' in your configuration, or set up an 'origin' git remote pointing to your github.com repository. Related issues github/pages-gem#399 jekyll/jekyll#4705
For me, the simple solution was to create a personal access token (I only checked the
And then added the dotenv gem to my Gemfile as such: