Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create CONTRIBUTING.md #642

Merged
merged 1 commit into from
Jul 11, 2016
Merged

Conversation

Manouchehri
Copy link
Contributor

There's a lot of bug reports where people don't even mention what build they're running.

@benhillis
Copy link
Member

This is a good suggestion, I will work with @russalex on getting this added.

@ghost
Copy link

ghost commented Jul 11, 2016

I would strongly suggest using an issue template as well, see: https://github.com/blog/2111-issue-and-pull-request-templates

@Manouchehri
Copy link
Contributor Author

Manouchehri commented Jul 11, 2016 via email

@jackchammons jackchammons merged commit 32a1325 into microsoft:master Jul 11, 2016
@sundhaug92
Copy link

A few suggestions:

  1. Indent the code-blocks in the example so that the numbering continues in the list
  2. Add a point for "expected behaviour", especially if there exists links to documentation/specification for "the Linux way"
  3. Change the text "the exact command" to "Steps required to reproduce", some bugs are not triggered by commands but rather by code written by the user themselves.
  4. Link people to a manual to write good bug-reports, to help people consider the how, why and whats of bug-reporting.
  5. Request that people tag their bugs so that it's easier to sort and filter through.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants