-
Notifications
You must be signed in to change notification settings - Fork 341
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
Fix warnings #65
Comments
I have a branch where I've fixed this, but it's a few commits ahead of other code that I submitted so I'm planning on waiting to submit a PR until my other PRs have been merged. |
That cool. Thank you. If its possible with your changes you could create a new branch and cherry-pick your commits into the new branch and create a PR :) |
I see this is closed but I am still getting similar errors.
|
I was able to overcome the errors by changing the "disable warnings" format in my config.yaml. This is the format that corrected the warnings:
Following is the existing format in the config.yaml, which still created errors :
I hope this helps others. |
I get the following warnings when I build the site:
(See also #61)
We should fix the warnings
The text was updated successfully, but these errors were encountered: