-
Notifications
You must be signed in to change notification settings - Fork 27
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
Improve tests #16
Comments
Currently, CI will verify that no URLs 404. Should be not so difficult to do something similar for Gems. |
@pathawks Before we make this the official home of all plugins & themes, let's come up with tests to enforce all the correct fields are present, etc. |
I'd like to create a test that makes sure anything claiming to be a Gem is actually listed on RubyGems.org |
We should exclude urls from We should type check all the YAML of themes and plugins. |
This issue has been automatically marked as stale because it has not been commented on for at least two months. The resources of the Jekyll team are limited, and so we are asking for your help. If this is a bug and you can still reproduce this error on the If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial. This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions. |
I wonder if we could whip something up that runs when the site is built on CI that verifies that all Gems exist, and URLs don't 404.
Seems like it’d be as easy as adding something to
_plugins/
The text was updated successfully, but these errors were encountered: