-
Notifications
You must be signed in to change notification settings - Fork 4
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
Validate GitHub issue templates #307
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry thought of one more thing
.pre-commit-config.yaml
Outdated
@@ -56,3 +56,12 @@ repos: | |||
args: | |||
- --fix=lf | |||
- id: trailing-whitespace | |||
- repo: https://github.com/python-jsonschema/check-jsonschema | |||
rev: cb934cfd6d2eea1aed7b20e4e9e6339d5952322c # 0.28.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume renovate
will use this syntax in the future. How does this play with pre-commit autoupdate
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😢 pre-commit autoupdate
doesn't like it, and just changes it back to a version number. So I've switched the SHAs to version numbers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I thought that might be the case. The pre-commit
maintainer is pretty stubborn, too, so he likely won't change the format.
This validates the GitHub issue tempaltes against a schema, and would have caught the issue that was fixed by #306.
Unfortunately it's not possible to validate the package template files as they contain invalid characters for a string entry (
{
and}
).