ef5ed242c9
* Create labelAdded-mapQuest.yml * Trim down repoman config * add metadata field to docs issue template * Create issueManagement-notTriaged.yml * handle needs more info * Create issueManagement-emptyIssue.yml * Update labelAdded-mapQuest.yml * Update issueManagement-notTriaged.yml * Create labelAdded-areaLabels.yml * Delete .github/workflows/issue-processing.yml * Update labelAdded-areaLabels.yml * Create pullRequestManagement-labelFiles.yml * Test * Use some other config that was previously working to check... * Restore and remove dupe pattern: * try adding qoutes * Remove reviewer request from labelFiles.yml * Add reviewer request for specific file patterns * Update reviewer request format in YAML file * Update PR management to assign guardrex * Change 'assignTo' to 'requestReview' in YAML * Remove PRMerger tool reference in metadata description |
||
---|---|---|
.github | ||
.vscode | ||
aspnetcore | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.markdownlint.json | ||
.openpublishing.publish.config.json | ||
.openpublishing.redirection.json | ||
.repoman.yml | ||
.whatsnew.json | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
LICENSE | ||
LICENSE-CODE | ||
README.md | ||
ThirdPartyNotices | ||
cspell.json | ||
quest-config.json |
README.md
ASP.NET Core Docs
This repository contains the ASP.NET Core documentation. See the Contributing Guide and the issues list if you would like to help.
ASP.NET 4.x documentation changes are made in the dotnet/AspNetDocs
GitHub repository.
How to open an issue
If the issue is with an ASP.NET Core document:
- Do not open a blank issue.
- Open the issue using the Open a documentation issue link and feedback form at the bottom of the article.
Using the Open a documentation issue link and form to open an issue adds article metadata for tracking, which indicates the article that you're commenting on and automatically pings the author for a faster response.
If the issue is:
- A simple typo or similar correction, you can submit a PR. See the contributor guide for instructions.
- A general support question, consider asking on a support forum site:
- A site design concern, create an issue at MicrosoftDocs/Feedback.
- A problem completing a tutorial, compare your code with the completed sample.
- A duplicate of an open or closed issue, leave a comment on that issue.