luke
/
sbt
mirror of https://github.com/sbt/sbt.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Good First Issues (markdown)

Dale Wijnand 2018-04-11 16:05:37 +01:00
parent f6da00230b
commit 2620e08d2d
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Good-First-Issues.md

@ -33,7 +33,7 @@ To convert an issue (e.g a [help wanted][] issue) so that it's ready for a new c
8. add links to pre-existing tests and give tips on how to test the change (if possible)
9. detail who the contributor can ask for help, and by which means ([sbt/sbt-contrib][], issue comments, etc)
10. make sure that any additional steps to take are explained or mentoring advice is given
11. finally, review the issue and see if you can make it more friendly and/or consise
11. finally, review the issue and see if you can make it more friendly and/or concise
In effect it should actually take longer to write the the issue than to fix it yourself (as an experienced
maintainer), but that extra time is an investment in [making sbt easier to contribute to][].