diff options
| author | fanquake <fanquake@gmail.com> | 2019-12-17 16:34:09 -0500 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2019-12-17 17:02:01 -0500 |
| commit | 6fef85bfa3cd7f76e83b8b57f9e4acd63eb664ec (patch) | |
| tree | b78845065893bbfad1e7ed20219088112fe1c881 | |
| parent | 47f45b677653c496a40acff00d11bd0e175ee058 (diff) | |
| parent | faede70882b4fd54390f5205dbe1dbcf019195c8 (diff) | |
Merge #17764: doc: Add formatting to the good first issue template
faede70882b4fd54390f5205dbe1dbcf019195c8 doc: Add formatting to the good first issue template (MarcoFalke)
Pull request description:
Add minor formatting to the good first issue template so that it is easier to see with one glance what the required skills are.
Preview is here: https://github.com/MarcoFalke/bitcoin-core/issues/new/choose
ACKs for top commit:
fanquake:
ACK faede70882b4fd54390f5205dbe1dbcf019195c8
Tree-SHA512: 0b0fcd051166981455061442e69f42c9fa726eaa228856e57434e012f7224781f4f3f12c31ce0a7a322df9999e79a8fbe63bf800b7933bc52c7cdaed90f37598
| -rw-r--r-- | .github/ISSUE_TEMPLATE/good_first_issue.md | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/.github/ISSUE_TEMPLATE/good_first_issue.md b/.github/ISSUE_TEMPLATE/good_first_issue.md index 6782218616..c441f7a307 100644 --- a/.github/ISSUE_TEMPLATE/good_first_issue.md +++ b/.github/ISSUE_TEMPLATE/good_first_issue.md @@ -7,13 +7,14 @@ assignees: '' --- -The purpose of the `good first issue` label is to highlight which issues are suitable for a new contributor without a deep understanding of the codebase. -Useful skills: +#### Useful skills: + +<!-- (For example, “C++11 std::thread”, “Qt5 GUI and async GUI design” or “basic understanding of Bitcoin mining and the Bitcoin Core RPC interface”.) --> -(For example, “C++11 std::thread”, “Qt5 GUI and async GUI design” or “basic understanding of Bitcoin mining and the Bitcoin Core RPC interface”.) +#### Want to work on this issue? -Want to work on this issue? +The purpose of the `good first issue` label is to highlight which issues are suitable for a new contributor without a deep understanding of the codebase. You do not need to request permission to start working on this. You are encouraged to comment on the issue if you are planning to work on it. This will help other contributors monitor which issues are actively being addressed and is also an effective way to request assistance if and when you need it. |