ilyakooo0/urbit
1
0
Fork 0
mirror of https://github.com/ilyakooo0/urbit.git synced 2024-08-15 13:40:31 +03:00
Code Issues Packages Projects Releases Wiki Activity

contributing: text fixup

Browse Source 
'clear' is preferred to "clear, obvious" here.
This commit is contained in:
Jared Tobin 2019-08-28 13:31:38 -02:30
parent e68f4a12cd
commit 1853311347
No known key found for this signature in database
GPG Key ID: 0E4647D58F8A69E4
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
CONTRIBUTING.md
View File

@ -211,11 +211,11 @@ bugs, performance problems, feature requests, and so on. If you encounter any
issues when developing on urbit, feel free to submit a report about it here.
A good bug report, description of a crash, etc., should ideally be
*reproducible*, with clear, obvious steps as to how another developer can
replicate and examine your problem. That said, this isn't always possible --
some bugs depend on having created a complicated or unusual state, or can
otherwise simply be difficult to trigger again (say, you encountered it in the
last continuity era).
*reproducible*, with clear steps as to how another developer can replicate and
examine your problem. That said, this isn't always possible -- some bugs
depend on having created a complicated or unusual state, or can otherwise
simply be difficult to trigger again (say, you encountered it in the last
continuity era).
Your issue should thus at a minimum be *informative*. The best advice here is
probably "don't write bad issues," where "bad" is a matter of judgment and