contributing: remove labelling discussion

In general contributors can't add labels to issues, so this section was
incorrect.
This commit is contained in:
Jared Tobin 2019-08-28 13:30:50 -02:30
parent 7d8b7435c5
commit e68f4a12cd
No known key found for this signature in database
GPG Key ID: 0E4647D58F8A69E4

View File

@ -210,11 +210,6 @@ The [GitHub tracker][issu] is our canonical source of truth around issues,
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.
You should label your issue appropriately if you know happen to know what it
applies to. For example, a `%gall` bug should be labelled with both 'gall' and
'bug'. It's ok if you don't know how to label your issue -- the maintainers
will help you out and try to label it appropriately.
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 --