Fixed #948 -- Added issue template. #951
Closed
Conversation
This file contains 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
|
Refs/Fixes #948 |
|
Oh. I didn't even see that issue. Great minds think alike, I suppose. 😬 |
|
Thanks for the compliment 😄 and for doing more than complain about it |
shaib
approved these changes
Sep 20, 2019
rixx
force-pushed
the
support
branch
2 times, most recently
from
3ddc567 to
7e6c149
Compare
Plenty of issues are opened on this repository by people mistaking this for the main Django issue tracker. Maybe some default text in the issue template, complete with documentation links, can help some of them.
|
Merged in a4a33ec. |
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.
This PR adds a default issue template that advises people opening an issue that this repository and its issue tracker are only for the djangoproject.com website, not for the Django project. It seems to me that this is a frequent reason for confusion, and this might help for at least some of the incoming issues.
You can see how this would look by opening an issue on my fork.
Comes with links to the docs on how to get help and how to open issues.
While I was creating the .github/ directory, I also added the
FUNDINGfile, which I copied from the main Django repository.