Add Feature Request, Good First Issue, and General Issue Templates#891
Merged
DanGould merged 1 commit intopayjoin:masterfrom Jul 22, 2025
Merged
Conversation
115da4f to
aa0e3bb
Compare
Collaborator
Pull Request Test Coverage Report for Build 16446746855Details
💛 - Coveralls |
DanGould
reviewed
Jul 21, 2025
aa0e3bb to
d379ae0
Compare
- [x] Add feature-request.yml to ISSUE_TEMPLATES
- [x] Add good first issue template
- [x] Add general issue template
Not all issues fit into one of our available templates (bug,
feature request, good first issue, etc.), this issue template
accounts for that.
d379ae0 to
29f5910
Compare
Collaborator
Author
|
@DanGould thanks for that catch, applied the two fixes (set multiple: true and add the |
DanGould
approved these changes
Jul 22, 2025
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
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.
Followup to #758. Adds the following issue templates mostly from their Bitcoin Core counterparts (excepting the "General" template):
It would probably be prudent for us to add SECURITY.md as well, but I'd need clarity on if we want to follow the pattern Bitcoin Core has established, and if so, which contributors should be contacted when reporting vulnerabilities and what methods of contact would be best (i.e. should we use a security issues dedicated email & PGP keys for contributors to whom issues can be reported).
Upon receiving that information if we would like to do this I will create
SECURITY.mdin a subsequent PR.