Merge branch 'BASE_DEV' into merge/v3_to_dev

.github/CODEOWNERS

@@ -38,5 +38,6 @@
 /whos-next-meeting-app @MSFT-yiz @HuihuiWu-Microsoft
 /teams-chef-bot @MSFT-yiz @HuihuiWu-Microsoft
 /spfx-productivity-dashboard @MSFT-yiz @HuihuiWu-Microsoft
+/react-retail-dashboard @MSFT-yiz @HuihuiWu-Microsoft
 /.config/samples-config-v3.json @HuihuiWu-Microsoft @wenytang-ms @tecton
 /.github/workflows/cd.yml @adashen @LongOddCode @Siglud @qinezh @wenytang-ms

.github/ISSUE_TEMPLATE/new-sample-onboard-request.md

@@ -0,0 +1,59 @@
+---
+name: New Sample Onboarding Request
+about: Collects the required information of new sample.
+title: "[Sample Onboard Request] Your sample name"
+labels: ''
+assignees: summzhan
+
+---
+
+**Owner:**
+Name and email address/GitHub account of maintainers. We will send email or @you in issues when there's any maintenance work to do in the future.
+
+**ID:**
+It should be same with folder name. E.g., "hello-world-sample".
+
+**Title:**
+Your sample name. E.g., "Hello World Sample"
+
+**Description:**
+One or two sentences to introduce this sample.
+
+**Onboard Date:**
+Estimated date to go online and show in Teams Toolkit sample gallery. E.g., 2023/11/01 or as soon as possible.
+
+**Tags:**
+You can give your samples a set of tags so that users can easily locate your sample from a group of samples. Those tags can be:
+- the programming languages you used, e.g. "JS", "TS", "C#" etc.
+- the Teams app type, e.g. "Tab", "Bot", "Message Extension" etc.
+- the highlighted technics you used, e.g. "React", "Azure Function", "Graph Toolkit", "Teams AI SDK", "Live Share SDK" etc.
+- the business scenarios of your sample, e.g. "Team Dashboard", "Productivity", "Notification", "Q&A" etc.
+You can customize the tag you used for your sample, the recommended number of tags is less than 5.
+
+**Time:**
+The estimation time to run the sample. E.g., "5mins to run".
+
+**Configuration:**
+Does the sample require additional manual steps to config before it can run? Please fill "Ready for local debug" or "Manual configurations required".
+
+**Thumbnail:**
+The file path where you put the thumbnail, typically it's in assets folder(assets/thumbnail.png) but you can put it anywhere you want.
+Suggested size of image is 1600x920/800x460 (If you have it with other sizes, please keep same image ratio for other sizes and don't forget to consider the resolution.)
+
+**(Optional) Demo GIF:**
+The file path where you put the GIF, typically it's in assets folder(assets/sampleDemo.gif) but you can put it anywhere you want.
+Suggested size of image is 1600x920/800x460 (If you have it with other sizes, please keep same image ratio for other sizes and don't forget to consider the resolution.
+Your GIF must fit the entire Teams client UI into the image.)
+
+**(Source code in this Repo) Source Code PR:**
+The link to pull request that contains sample source codes.
+
+**(Source code NOT in this Repo) Sample URL:**
+The URL if your sample code resides in another sample repo. It's better to use a tag instead of a branch for stablility.
+E.g., "https://github.com/xxx/xxx/tree/v1.0/xxx".
+
+**(Optional) Minimum Teams Toolkit Version:**
+Teams Toolkit version requirement to run the sample - minimum version
+
+**(Optional) Maximum Teams Toolkit Version:**
+Teams Toolkit version requirement to run the sample - maximum version

.github/policies/issueCommentManagement.yml

@@ -0,0 +1,31 @@
+id: issueCommentManagement.issueCommentOpened
+name: GitOps.issueCommentManagement
+description: Handlers for when an issue comment is first opened
+owner:
+resource: repository
+disabled: false
+where:
+configuration:
+  resourceManagementConfiguration:
+    eventResponderTasks:
+      - description: add needs attention label to issue if there is a new comment by a non-member
+        if:
+          - payloadType: Issue_Comment
+          - and:
+            - isOpen
+            - isIssue
+            - not:
+                or:
+                  - hasLabel:
+                      label: needs attention
+                  - activitySenderHasAssociation:
+                      association: Member
+                  - isActivitySender:
+                      user: msftbot[bot]
+                      issueAuthor: False
+                  - isActivitySender:
+                      user: microsoft-github-policy-service[bot]
+                      issueAuthor: False
+        then:
+          - addLabel:
+              label: needs attention

.github/policies/resourceManagement.yml

@@ -0,0 +1,250 @@
+id: 
+name: GitOps.PullRequestIssueManagement
+description: GitOps.PullRequestIssueManagement primitive
+owner: 
+resource: repository
+disabled: false
+where: 
+configuration:
+  resourceManagementConfiguration:
+    scheduledSearches:
+    - description: 
+      frequencies:
+      - weekday:
+          day: Monday
+          time: 0:0
+      - weekday:
+          day: Tuesday
+          time: 0:0
+      - weekday:
+          day: Wednesday
+          time: 0:0
+      - weekday:
+          day: Thursday
+          time: 0:0
+      - weekday:
+          day: Friday
+          time: 0:0
+      filters:
+      - isIssue
+      - isOpen
+      - hasLabel:
+          label: needs more info
+      - isNotLabeledWith:
+          label: no recent activity
+      - isNotLabeledWith:
+          label: bug
+      - isNotLabeledWith:
+          label: feature-request
+      - noActivitySince:
+          days: 7
+      actions:
+      - addLabel:
+          label: no recent activity
+      - addReply:
+          reply: >
+            This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **7 days**. It will be closed if no further activity occurs **within 3 days of this comment**. If it *is* closed, feel free to comment when you are able to provide the additional information and we will re-investigate.
+    - description: 
+      frequencies:
+      - weekday:
+          day: Monday
+          time: 0:0
+      - weekday:
+          day: Tuesday
+          time: 0:0
+      - weekday:
+          day: Wednesday
+          time: 0:0
+      - weekday:
+          day: Thursday
+          time: 0:0
+      - weekday:
+          day: Friday
+          time: 0:0
+      filters:
+      - isOpen
+      - isIssue
+      - noActivitySince:
+          days: 3
+      - hasLabel:
+          label: no recent activity
+      - hasLabel:
+          label: needs more info
+      - isNotInAnyMilestone
+      - isNotLabeledWith:
+          label: bug
+      - isNotLabeledWith:
+          label: feature-request
+      actions:
+      - closeIssue
+      - addReply:
+          reply: 'Due to lack of details for further investigation, we will archive the issue for now. In case you still have following-up questions on this issue, please always feel free to reopen the issue by clicking ‘reopen issue’ button below the comment box. We will get back to you as soon as possible. '
+    - description: 
+      frequencies:
+      - weekday:
+          day: Monday
+          time: 0:0
+      - weekday:
+          day: Tuesday
+          time: 0:0
+      - weekday:
+          day: Wednesday
+          time: 0:0
+      - weekday:
+          day: Thursday
+          time: 0:0
+      - weekday:
+          day: Friday
+          time: 0:0
+      filters:
+      - isIssue
+      - isOpen
+      - hasLabel:
+          label: needs more info
+      - hasLabel:
+          label: bug
+      - isNotLabeledWith:
+          label: no recent activity
+      - noActivitySince:
+          days: 7
+      actions:
+      - addLabel:
+          label: no recent activity
+      - addReply:
+          reply: >
+            This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **7 days**. As it is labeled with bug, it will be manually handled
+    - description: 
+      frequencies:
+      - weekday:
+          day: Monday
+          time: 0:0
+      - weekday:
+          day: Tuesday
+          time: 0:0
+      - weekday:
+          day: Wednesday
+          time: 0:0
+      - weekday:
+          day: Thursday
+          time: 0:0
+      - weekday:
+          day: Friday
+          time: 0:0
+      filters:
+      - isIssue
+      - isOpen
+      - hasLabel:
+          label: needs more info
+      - hasLabel:
+          label: feature-request
+      - isNotLabeledWith:
+          label: no recent activity
+      - noActivitySince:
+          days: 7
+      actions:
+      - addLabel:
+          label: no recent activity
+      - addReply:
+          reply: >
+            This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **7 days**. As it is labeled with feature-request, it will be manually handled
+    - description: 
+      frequencies:
+      - daily:
+          time: 1:0
+      filters:
+      - isOpen
+      - isIssue
+      - noActivitySince:
+          days: 1
+      - hasLabel:
+          label: close-wait
+      - isNotLabeledWith:
+          label: bug
+      - isNotLabeledWith:
+          label: feature-request
+      - isNotInAnyMilestone
+      actions:
+      - closeIssue
+      - removeLabel:
+          label: close-wait
+    eventResponderTasks:
+    - if:
+      - payloadType: Issues
+      - isAction:
+          action: Opened
+      then:
+      - addReply:
+          reply: Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.
+      description: 
+    - if:
+      - payloadType: Issues
+      - hasLabel:
+          label: no recent activity
+      - not:
+          isAction:
+            action: Closed
+      then:
+      - removeLabel:
+          label: no recent activity
+      description: 
+    - if:
+      - payloadType: Issue_Comment
+      - hasLabel:
+          label: no recent activity
+      then:
+      - removeLabel:
+          label: no recent activity
+      description: 
+    - if:
+      - payloadType: Issue_Comment
+      - isOpen
+      - hasLabel:
+          label: needs more info
+      - isAction:
+          action: Created
+      - isActivitySender:
+          issueAuthor: True
+      then:
+      - removeLabel:
+          label: needs more info
+      - addLabel:
+          label: needs attention
+      description: 
+    - if:
+      - payloadType: Issues
+      - isAction:
+          action: Opened
+      - or:
+        - bodyContains:
+            pattern: 'API call to Developer Portal failed: (.*) API name: (.*), X-Correlation-ID: (.*).'
+            isRegex: True
+        - bodyContains:
+            pattern: Failed to (.*) teams app in app studio, due to \d{3}, .*
+            isRegex: True
+      then:
+      - addLabel:
+          label: upstream
+      - assignIcmUsers:
+          teamId: 97190
+          primary: True
+          secondary: False
+      - addReply:
+          reply: Sorry for the inconvenience! Based on the info provided, the issue is caused by the API failure from Teams Developer Portal. We will inform you once we get any updates.
+      description: 
+    - if:
+      - payloadType: Issues
+      - hasLabel:
+          label: close-wait
+      - not:
+          isActivitySender:
+            user: github-actions[bot]
+            issueAuthor: False
+      - not:
+          isAction:
+            action: Closed
+      then:
+      - removeLabel:
+          label: close-wait
+      description: 
+onFailure: 
+onSuccess: