Fix unclear error message regarding the citation of issues in example…#4688
Merged
Conversation
… files (schemaorg#4687) The previous error message was unclear regarding the requirements of an example file. This commit: - references the contribution guidelines - raises a more defined error message in github actions Closes schemaorg#4687
Contributor
Author
MatthiasWiesmann
approved these changes
Jan 15, 2026
Github included the closing bracket inside the link, this commit avoids that to make the link in the error messages clickable.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
… files (#4687)
The previous error message (
TYPES does not start with example frag: #{types}) was unclear regarding the requirements of an example file. This commit:Closes #4687
Error now looks like this:
Example:
Job with failure due to missing issue number on example
Screenshot:
