We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Acceptance criteria Create an issue template for this repository so contributors can communicate well about what the issue is 👍
Documentation These are the new instructions for creating issue templates, but they require using the internal editing process in github's UI: https://help.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository
I'm leaning more toward the legacy method where we write our own file: https://help.github.com/en/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository
But I'd like to see who picks up this task and what their thoughts are!
The text was updated successfully, but these errors were encountered:
@MicheleCynowicz I'd like to grab this issue 😃
Sorry, something went wrong.
Merge pull request #149 from FarhiaM/master
8a305a6
Create an Issue Template for this repository #142
FarhiaM
Successfully merging a pull request may close this issue.
Acceptance criteria
Create an issue template for this repository so contributors can communicate well about what the issue is 👍
Documentation
These are the new instructions for creating issue templates, but they require using the internal editing process in github's UI: https://help.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository
I'm leaning more toward the legacy method where we write our own file: https://help.github.com/en/github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository
But I'd like to see who picks up this task and what their thoughts are!
The text was updated successfully, but these errors were encountered: