Initial repo config (#9)

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: docs.microsoft.com site feedback
+    url: https://github.com/MicrosoftDocs/feedback/issues/new/choose
+    about: Log general docs.microsoft.com site issues here
+  - name: .NET platform and other product feedback
+    url: https://developercommunity.visualstudio.com/spaces/61/index.html
+    about: Log product issues here

.github/ISSUE_TEMPLATE/doc-issue.md

@@ -0,0 +1,36 @@
+---
+name: .NET doc issue
+about: Report a problem in the .NET documentation
+---
+
+**Before you open an issue**
+
+If the issue is:
+
+- A simple typo or similar correction, consider submitting a PR to fix it instead of logging an issue. See [the contributor guide](https://docs.microsoft.com/contribute/#quick-edits-to-existing-documents) for instructions.
+- A general support question, consider asking on a support forum site.
+- A site design concern, create an issue at [MicrosoftDocs/feedback](https://github.com/MicrosoftDocs/feedback/issues/new/choose).
+- 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.
+
+**Issue description**
+
+<include description here>
+
+**Target framework**
+
+Check the .NET target framework(s) being used, and include the version number(s).
+
+- [ ] .NET Core
+- [ ] .NET Framework
+- [ ] .NET Standard
+
+If using the .NET Core SDK, include `dotnet --info` output. If using .NET Framework without the .NET Core SDK, include info from Visual Studio's **Help** > **About Microsoft Visual Studio** dialog.
+
+<details>
+<summary><strong>dotnet --info output</strong> or <strong>About VS info</strong></summary>
+
+```console
+<replace>
+```
+</details>

.github/ISSUE_TEMPLATE/docs-request.md

@@ -0,0 +1,16 @@
+---
+name: .NET doc request
+about: Request a new article to provide missing information
+---
+
+**Help us make content visible**
+
+- Tell us what search terms you used and how you searched docs.
+- Tell us what docs you found that didn't address your concern.
+
+**Describe the new article**
+
+- Explain why this article is needed.
+- Suggest a location in the Table of Contents.
+- Write an abstract. In one **short** paragraph, describe what this article will cover.
+- Create an outline for the new article. We'll help review the outline and approve it before anyone writes the article.

.github/ISSUE_TEMPLATE/dotnet-breaking-change.md

@@ -0,0 +1,92 @@
+---
+name: .NET Core breaking change
+about: Report a change in .NET Core that breaks something that worked in a previous version (intended mostly for product-team use)
+---
+
+<!--
+This issue template is for use in creating issues that document breaking changes. This template can be used to create an issue:
+
+- By Microsoft product team members who are documenting a breaking change.
+
+- By Microsoft customers who are experiencing a compatibility issue between .NET Framework and .NET Core or between versions of .NET Core.
+
+Text in brackets is a placeholder; replace the text with the requested information and remove the brackets before submitting the issue.
+
+Also, remove this comment before submitting the issue.
+-->
+
+## [Change title]
+
+[Brief description of the change]
+
+### Version introduced
+
+[Version in which the breaking change first occurred (for example, 3.0 for .NET Core 3.0)]
+
+### Old behavior
+
+### New behavior
+
+### Reason for change
+
+### Recommended action
+
+[ Suggested steps if user is affected go here:
+- Possible workarounds
+- Example of code changes to handle change
+]
+
+### Category
+
+[Choose a category from one of the following:
+
+- ASP.NET Core
+- C#
+- Core .NET libraries
+- Cryptography
+- Data
+- Debugger
+- Deployment
+- Globalization
+- Interop
+- JIT
+- LINQ
+- Managed Extensibility Framework (MEF)
+- MSBuild
+- Networking
+- Printing
+- Security
+- Serialization
+- Visual Basic
+- Windows Forms
+- Windows Presentation Foundation (WPF)
+- XML, XSLT
+]
+
+### Affected APIs
+
+[ If no APIs are affected, this should read:
+     "Not detectable via API analysis"
+
+  If affected APIs are identifiable, include a link for each. The link takes the form:
+
+  `[friendly description of API](link to API on docs.microsoft.com)`
+
+  For example, `[String.IndexOf(String)](https://docs.microsoft.com/dotnet/api/system.string.indexof#System_String_IndexOf_System_String_)
+
+  For methods, if all overloads are affected, link to the general overloaded method page. For example:
+
+  <https://docs.microsoft.com/dotnet/api/system.string.indexof>
+
+  Otherwise, link to the individual method overload. For example:
+
+  <https://docs.microsoft.com/dotnet/api/system.string.indexof#System_String_IndexOf_System_String_>
+
+]
+
+<!-- Do not modify anything below this line -->
+
+---
+#### Issue metadata
+
+* Issue type: breaking-change