One of the easiest ways to contribute is to participate in discussions and discuss issues. You can also contribute by submitting pull requests with code changes.
Please start a discussion or log a new issue on the Home repo issue tracker.
When filing issues, please consider using this sample bug filing template from the ASP.Net team. The best way to get your bug fixed is to be as detailed as you can be about the problem. Providing steps to reproduce the problem is ideal. Here are questions you can answer before you file a bug to make sure you're not missing any important information.
- Did you read the documentation?
- Did you include the snippet of broken code in the issue?
- What are the EXACT steps to reproduce this problem?
- What package versions are you using (you can see these in the
project.jsonfile)? - What operating system are you using?
- What version of Visual Studio are you using?
GitHub supports markdown, so when filing bugs make sure you check the formatting before clicking submit.
If you don't know what a pull request is read this article: https://help.github.com/articles/using-pull-requests. You might also read these two blogs posts on contributing code: Open Source Contribution Etiquette by Miguel de Icaza and Don't "Push" Your Pull Requests by Ilya Grigorik.
Commit/Pull Request Format
Summary of the changes (Less than 80 chars)
- Detail 1
- Detail 2
#bugnumber (in this specific format)