Repository navigation
Add a code of conduct, a security note, and issue and pull request templates - #4
Merged
Merged
Conversation
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.
GitHub's community profile for this repo is at 57%: it has a README, a license, CONTRIBUTING.md and a description, but no code of conduct, issue templates or pull request template. Three good first issues are open, so this adds the missing pieces before someone picks one up.
Changes
CODE_OF_CONDUCT.md: four short rules, and how to report a problem by email.SECURITY.md: says the repo runs no server, reads no secrets and makes no network calls, and asks for security problems by email, not in a public issue..github/ISSUE_TEMPLATE/new-kernel.yml: a "Propose a kernel" form (what the kernel computes and how the work is split, the NumPy reference, and whether it is CUDA, Triton or a reference only)..github/ISSUE_TEMPLATE/wrong-result.yml: a "Report a wrong result" form (file, command and output, GPU, CUDA and Python versions)..github/ISSUE_TEMPLATE/config.yml: keeps blank issues allowed..github/pull_request_template.md: Problem, Change and Testing sections; Testing asks for the reference's PASS line, the last line ofcheck_all.pyand the nvcc build command, plus the GPU and CUDA version if the kernel was run on a GPU.README.mdandCONTRIBUTING.md: one sentence each that links the code of conduct and the issue forms; CONTRIBUTING also points to SECURITY.md.No kernel, reference or CI changes.
Testing
Before this change:
The two issue forms load as YAML:
GitHub only checks issue forms on the default branch, so the forms show up in the New issue menu after the merge.