Merge branch 'main' into user/chingucoding/menubar-disabled-arrowbeha…

…vior

.config/tsaoptions.json

@@ -0,0 +1,9 @@
+{
+    "instanceUrl": "https://microsoft.visualstudio.com",
+    "projectName": "os",
+    "areaPath": "OS\\Windows Client and Services\\ADEPT\\OWL (Open Windows pLatform)\\Controls",
+    "iterationPath": "OS",
+    "notificationAliases": [ "uxpct@microsoft.com" ],
+    "ignoreBranchName": true,
+    "codebaseName": "microsoft_microsoft-ui-xaml"
+}

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,58 @@
+name: Bug report
+description: File a bug report
+title: "Bug title"
+labels: [bug]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        For bugs related to UWP or the app models, please open a bug on the [Windows App SDK repository](https://github.com/microsoft/WindowsAppSDK)
+  - type: textarea
+    validations:
+      required: true
+    attributes:
+      label: Describe the bug
+      description: Please enter a short, clear description of the bug.
+  - type: textarea
+    validations:
+      required: true
+    attributes:
+      label: Steps to reproduce the bug
+      description: Please provide any required setup and steps to reproduce the behavior.
+      placeholder: |
+        1. Go to '...'
+        2. Click on '....'
+  - type: textarea
+    attributes:
+      label: Expected behavior
+      description: Please provide a description of what you expected to happen
+  - type: textarea
+    attributes:
+      label: Screenshots
+      description: If applicable, add screenshots here to help explain your problem
+  - type: dropdown
+    attributes:
+      label: NuGet package version
+      description: If you are seeing your issue on older versions please try the latest release
+      options:
+        - "WinUI 3 - Windows App SDK 1.3.3: 1.3.230724000"
+        - "WinUI 3 - Windows App SDK 1.4 Preview 1: 1.4.230628000-preview1"
+        - "WinUI 3 - Windows App SDK 1.4 Experimental 1: 1.4.230518007-experimental1"
+        - "WinUI 2 - Microsoft.UI.Xaml 2.8.2"
+  - type: dropdown
+    attributes:
+      label: Windows version
+      description: Which Windows versions did you see the issue on?
+      multiple: true
+      options:
+        - "Windows Insider Build (xxxxx)"
+        - "Windows 11 (22H2): Build 22621"
+        - "Windows 11 (21H2): Build 22000"
+        - "Windows 10 (21H2): Build 19044"
+        - "Windows 10 (21H1): Build 19043"
+        - "Windows 10 (20H2): Build 19042"
+        - "Windows 10 (1809): Build 17763"
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Enter any other applicable info here

.github/ISSUE_TEMPLATE/feature_proposal.md

@@ -14,7 +14,7 @@ For feature proposals related to UWP or the app models, please open an issue on
 It's fine if you don't have all the details: you can start with the Summary and Rationale.
 
 This link describes the WinUI feature/API proposal process:
-https://github.com/Microsoft/microsoft-ui-xaml/blob/master/docs/feature_proposal_process.md
+https://github.com/Microsoft/microsoft-ui-xaml/blob/main/docs/feature_proposal_process.md
 -->
 
 # Proposal: [your title here] 
@@ -27,7 +27,7 @@ https://github.com/Microsoft/microsoft-ui-xaml/blob/master/docs/feature_proposal
 <!-- Create a list that describes WHY the feature should be added to WinUI for all developers and users.
 Proposals often have multiple motives for why we should do the work, so list each one as a separate bullet.
 If applicable you can also describe how the proposal aligns to the current WinUI roadmap and priorities in a separate paragraph:
-https://github.com/Microsoft/microsoft-ui-xaml/blob/master/docs/roadmap.md
+https://github.com/Microsoft/microsoft-ui-xaml/blob/main/docs/roadmap.md
 -->
 * {First reason for why we should consider this proposal}
 * {Second reason for why we should consider this proposal}
@@ -36,7 +36,7 @@ https://github.com/Microsoft/microsoft-ui-xaml/blob/master/docs/roadmap.md
 
 <!----------------------
 The below sections are optional when submitting an idea or proposal.
-All sections are required before we'll accept a PR to master, but aren't necessary to start the discussion.
+All sections are required before we'll accept a PR to main, but aren't necessary to start the discussion.
 ------------------------>
 
 ## Scope

.github/ISSUE_TEMPLATE/winui-toolkit-bug-report.md

@@ -0,0 +1,26 @@
+---
+name: WinUI Design Toolkit Bug report
+about: File a WinUI Design Toolkit bug report
+title: 'WinUI Design Toolkit Bug: [descriptive bug title here]'
+labels: area-DesignToolkit, team-Design
+assignees: ''
+
+---
+
+## WinUI Toolkit Bug Report
+
+---
+
+<!--Please use this template to report a bug in the WinUI Design Toolkit. -->
+
+**Name of component or part of Toolkit:**
+<!-- Please indicate which control you are reporting  -->
+
+**Describe the bug:**
+<!-- Please enter a short, clear description of the bug -->
+
+**Version Info:**
+<!-- Please indicate which version of the toolkit you are using -->
+
+**Additional context:**
+<!-- Enter any other applicable info here -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -6,7 +6,7 @@
 ## Motivation and Context
 <!--- Why is this change required? What problem does it solve? -->
 <!--- If it fixes an open issue, please link to the issue here. -->
-<!--- Use the syntax "Closes #1234" or "Fixes #5678" so that GitHub will close the issue once the PR is complete. -->
+<!--- Use the syntax "Closes #xxx" or "Fixes #xxx" so that GitHub will close the issue once the PR is complete. -->
 
 ## How Has This Been Tested?
 <!--- Please describe how you tested your changes. -->