Adding issue templates to repo #374
Merged
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.
This PR adds:
New Issue
for an exampleThe
.yml
files and directory structure follow the issue form syntax/structure described here https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-formsA lot of this was lifted from the way the
huggingface_hub
repository structures these templates - see here: https://github.com/huggingface/huggingface_hub/tree/main/.github/ISSUE_TEMPLATE - and then modified for some of the more common things we ask (machine info; HF_XET envvars, etc)This symmetry between
huggingface_hub
and this repo was intentional so community members aren't started by a completely different format for providing information when opening an issue/asking for a feature.