it could include a link to that exact file in the PR branch, such that a maintainer could click to edit
as the output is for humans, it seems like rendering title, description, etc. as Markdown would be valuable.
however, as it was written (or dumped to) JSON Schema, it's would possible to generate a canonical link to the generated documentation for that schema item, once available
similarly, the raw repr that gets dumped could be a table
or, indeed, the whole thing could be a table
it may be worth putting these inside details tags
Now all we gotta do is schematize the other user-edited .yml :)
Some notes [about the linter]:
title
,description
, etc. as Markdown would be valuable.details
tagsNow all we gotta do is schematize the other user-edited
.yml
:)Originally posted by @bollwyvl in https://github.com/conda-forge/conda-smithy/issues/1756#issuecomment-1999542510