chore: remove issue template overrides #138
Open
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
katie-perry
added
chore
Member
|
Do we need to remove from python/{{cookiecutter.project_slug}}/.github/ISSUE_TEMPLATE? |
Contributor
Author
you are on top of it today! great catch - removed :D |
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.
So it turns out, any repo within an organization will use any .github default defined in a repo like this: https://github.com/GenomicMedLab/.github
This PR removes the ISSUE_TEMPLATE folder so each repo will simply use the org default ones as defined above. If any overrides are needed and are repo-specific, simply add back ISSUE_TEMPLATE with the files and edit any lines as you need for the repo.
If this gets left in, any repo created with this template will automatically contain the folder and identical files that would act as overrides, so they'd need manually updated any time changes are made to the org-wide templates. So removal will make for less work in the future if we ever want to change the templates!