Issue Template config #3
Draft
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
|
We can also point folks to the Node slack or other places with active q/a |
wesleytodd
approved these changes
Jun 11, 2020
bjohansebas
reviewed
Sep 14, 2024
Co-authored-by: Sebastian Beltran <[email protected]>
|
@jonchurch anything holding this up or can we merge this? |
|
We got the email setup today. Which PR were we pending on this so I can make sure to drop the new reporting email in? |
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 draft PR introduces a
config.yml. See Github docs here.As is, this PR does two things:
blank_issues_enabled: false)Everything about this config is up for debate. Currently the linked page doesn't clearly state an email address, which is something we can address elsewhere.