Revert issue template changes to use organisation issue template #211
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
3 participants
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.
I originally intended to add issue templates in every single repository with blank issues disabled, see reactphp/reactphp#466 for whole discussion.
After I started implementing issue templates in a few repositories, I came to the realisation that it would be more wise to introduce issue templates on an organisational level, to keep future adjustments for these templates rather small and simple. You can read more about my intentions in reactphp/.github#3.
I now have to revert my changes in some of these projects, because they're currently overwriting the organisational issue templates:
This PR removes the
ISSUE_TEMPLATEfolder and allows the organisational issue templates to take their place. This will also add the possibility to create blank issues.This PR builds on top of #209 and reactphp/.github#3.
Refs: reactphp/http#479