chore(workflows): add types and website area field automatically (#4341)

* chore(workflows): add types and website area field automatically

* add env variables

* add docs type

* move type docs

.github/ISSUE_TEMPLATE/accessibility-issue.md

@@ -1,9 +1,10 @@
 ---
 name: Accessibility issue ♿
 about: Report an accessibility or usability issue
-title: ""
-labels: "type: a11y ♿"
-assignees: ""
+title: ''
+type: 'bug'
+labels: ['type: a11y ♿', 'status: needs triage 🕵️‍♀️']
+assignees: ''
 ---
 
 <!-- Feel free to remove sections that aren't relevant.

.github/ISSUE_TEMPLATE/bug-report.md

@@ -1,9 +1,10 @@
 ---
-name: "Bug report 🐛"
+name: 'Bug report 🐛'
 about: Create a report to help us improve
-title: ""
-labels: "type: bug 🐛"
-assignees: ""
+title: ''
+type: 'bug'
+labels: ['type: bug 🐛', 'status: needs triage 🕵️‍♀️']
+assignees: ''
 ---
 
 <!-- Feel free to remove sections that aren't relevant.
@@ -16,7 +17,8 @@ assignees: ""
 
 > Describe in detail the issue you're having.
 
-> What did you expect to happen? What happened instead? What would you like to see changed?
+> What did you expect to happen? What happened instead? What would you like to
+> see changed?
 
 > What browser are you working in?
 

.github/ISSUE_TEMPLATE/component-accessibility-deliverables.yaml

@@ -1,7 +1,8 @@
 name: Component accessibility deliverables
 description: Submit the accessibility portion of your component
 title: '[Component name] component – accessibility '
-labels: 'accessibility'
+type: 'task'
+labels: ['accessibility', 'status: needs triage 🕵️‍♀️']
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/docs-issue.yaml

@@ -2,7 +2,8 @@ name: Documentation issue 📖
 description:
   Report missing, incorrect, or otherwise inconsistent documentation here.
 title: '[Docs]: '
-labels: 'type: bug 🐛'
+type: 'bug'
+labels: ['type: bug 🐛', 'type: docs 📖', 'status: needs triage 🕵️‍♀️']
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/feature-request.md

@@ -1,43 +1,52 @@
 ---
-name: "Feature request 💡"
+name: 'Feature request 💡'
 about: Suggest an idea for this project
-title: ""
-labels: "type: enhancement 💡"
-assignees: ""
+title: ''
+type: 'enhancement'
+labels: ['type: enhancement 💡', 'status: needs triage 🕵️‍♀️']
+assignees: ''
 ---
 
-Use this template if you want to request a new feature, or a change to an existing feature.
+Use this template if you want to request a new feature, or a change to an
+existing feature.
 
 If you are reporting a bug or problem, please use the bug template instead.
 
 ### Summary
 
 Please describe your request in one or two sentences.
 
-Clarify if you are asking for both design and development, or just design, or just development.
+Clarify if you are asking for both design and development, or just design, or
+just development.
 
 ### Justification
 
 Provide the business reasons for this request.
 
 ### Desired UX and success metrics
 
-Describe the full user experience for this feature. Also define the metrics by which we can measure success/failure for the user.
+Describe the full user experience for this feature. Also define the metrics by
+which we can measure success/failure for the user.
 
 ### Must-have functionality
 
 Highlight any "must have" needs and functionality for the request.
 
-This should not be a full list of functionality; the Carbon team will work with you to define functionality based on the desired UX.
+This should not be a full list of functionality; the Carbon team will work with
+you to define functionality based on the desired UX.
 
 ### Specific timeline issues / requests
 
-Do you want this work within a specific time period? Is it related to an upcoming release?
+Do you want this work within a specific time period? Is it related to an
+upcoming release?
 
-_NB: The Carbon team will try to work with your timeline, but it's not guaranteed. The earlier you make a request in advance of a desired delivery date, the better!_
+_NB: The Carbon team will try to work with your timeline, but it's not
+guaranteed. The earlier you make a request in advance of a desired delivery
+date, the better!_
 
 ### Available extra resources
 
 What resources do you have to assist this effort?
 
-_Carbon is a collaborative system. We encourage teams to build components and submit them for integration as either add-ons or core components._
+_Carbon is a collaborative system. We encourage teams to build components and
+submit them for integration as either add-ons or core components._

.github/ISSUE_TEMPLATE/feedback.md

@@ -1,8 +1,9 @@
 ---
 name: Website feedback
 about: User feedback collected from the Carbon Design System Website.
-labels: "type: discussion 💬"
-assignees: ""
+type: 'task'
+labels: ['type: discussion 💬', 'status: needs triage 🕵️‍♀️']
+assignees: ''
 ---
 
 <!--

.github/ISSUE_TEMPLATE/question.md

@@ -1,9 +1,10 @@
 ---
 name: Question ❓
 about: Usage question or discussion about the Carbon Design System Website.
-title: ""
-labels: "type: question ❓"
-assignees: ""
+title: ''
+type: 'task'
+labels: ['type: question ❓', 'status: needs triage 🕵️‍♀️']
+assignees: ''
 ---
 
 <!--

.github/workflows/issue-triage.yml

@@ -4,9 +4,46 @@ on:
     types: [opened]
   issue_comment:
     types: [created]
+env:
+  ISSUE_NUMBER: ${{ github.event.issue.number }}
+  OWNER: ${{ github.repository_owner }}
+  REPOSITORY: ${{ github.repository }}
+
+  PROJECT_ID: 39
+  ITEM_FETCH_LIMIT: 1200
+
+  AREA_FIELD_ID: PVTSSF_lADOAYA3Ss1Nv84BfRL4
+  AREA_WEBSITE: 113a0859
 jobs:
   issue-triage:
     uses: carbon-design-system/carbon/.github/workflows/issue-triage.yml@main
     secrets:
       APP_ID: ${{ secrets.APP_ID }}
       APP_PRIVATE_KEY: ${{ secrets.APP_PRIVATE_KEY }}
+  set-area-per-repo:
+    needs: setup-variables
+    runs-on: ubuntu-latest
+    if: ${{ github.event_name == 'issues' && github.event.action == 'opened' }}
+    steps:
+      - uses: actions/create-github-app-token@v1
+        id: app-token
+        with:
+          app-id: ${{ secrets.APP_ID }}
+          private-key: ${{ secrets.PRIVATE_KEY }}
+      - name: Get issue ID
+        id: get_issue_id
+        run: |
+            ISSUE_ID=$(gh project item-list $PROJECT_ID --owner=$OWNER --limit=$ITEM_FETCH_LIMIT --format=json --jq ".items[] | select(.content.number == $ISSUE_NUMBER and .content.repository == $REPOSITORY) | .id" -r)
+            if [ -z "$ISSUE_ID" ]; then
+              echo "Issue ID not found for issue number $ISSUE_NUMBER"
+              exit 1
+            fi
+            echo "Issue ID is $ISSUE_ID"
+            echo "issue_id=$ISSUE_ID" >> "$GITHUB_OUTPUT"
+      - name: Update issue with website area field
+        run:
+          gh project item-edit --project-id $PROJECT_ID --id $ISSUE_ID
+          --field-id $AREA_FIELD_ID --single-select-option-id $AREA_WEBSITE
+        env:
+          GH_TOKEN: ${{ steps.app-token.outputs.token }}
+          $ISSUE_ID: ${{ steps.get_issue_id.outputs.issue_id }}