build: Use prettier for yaml

Stop ignoring .yml files in prettier and fix existing issues.

.github/ISSUE_TEMPLATE/DMP_2024_DESIGN.yml

@@ -1,7 +1,7 @@
 name: DMP 2024 Design Project Template
 description: List a new design project for Dedicated Mentoring Program 2024
-title: "[DMP 2024]: "
+title: '[DMP 2024]: '
-labels: ["DMP 2024" , "Product Usability"]
+labels: ['DMP 2024', 'Product Usability']
 body:
   - type: textarea
     id: ticket-description
@@ -10,7 +10,7 @@ body:
     attributes:
       label: Description
       description: Provide a brief description of the problem statement here. Include any relevant context or background information (user research findings, list of user personas / target users affected, etc.,.)
-  
+
   - type: textarea
     id: key-design-research-questions
     validations:
@@ -25,14 +25,14 @@ body:
       required: true
     attributes:
       label: Current State
-      description: Describe the current state of the problem. What are the gaps / unanswered questions wrt problem statements identified? What is the user experience like currently? 
+      description: Describe the current state of the problem. What are the gaps / unanswered questions wrt problem statements identified? What is the user experience like currently?
 
   - type: textarea
     id: desired-state
     validations:
       required: true
     attributes:
-      label: Desired State 
+      label: Desired State
       description: What is the roadmap for the intended users and the respective product? Please list if there are any product / feature specific expected goals. (These could be overall and not limited to the DMP project goals)
 
   - type: textarea
@@ -41,7 +41,7 @@ body:
       required: true
     attributes:
       label: Goals & Mid-Point Milestone
-      description: List the goals of the project (What is the expected end outcome from the project). Add the tasks that must be completed by Mid-point check-in i.e 1.5 months into the execution period 
+      description: List the goals of the project (What is the expected end outcome from the project). Add the tasks that must be completed by Mid-point check-in i.e 1.5 months into the execution period
       value: |
         ## Goals
         - [ ] [Goal 1]
@@ -102,10 +102,10 @@ body:
         - Ushahidi
         - Arghyam
         - Piramal Swasthya Management Research Institute
-        - Dimagi 
+        - Dimagi
-        - Win Over Cancer 
+        - Win Over Cancer
-        - Protean 
+        - Protean
-        - Thoughtworks 
+        - Thoughtworks
     validations:
       required: true
 
@@ -114,11 +114,11 @@ body:
     attributes:
       label: Domain
       options:
-        - ⁠Healthcare 
+        - ⁠Healthcare
         - ⁠Education
         - Financial Inclusion
         - ⁠Livelihoods
-        - ⁠Skilling 
+        - ⁠Skilling
         - ⁠Learning & Development
         - ⁠Agriculture
         - ⁠Service Delivery
@@ -134,4 +134,3 @@ body:
       description: Please tag relevant mentors for the ticket
     validations:
       required: true
-  

.github/workflows/build.yml

@@ -4,9 +4,9 @@ name: build-run
 on:
   # Triggers the workflow on push or pull request events but only for the main branch
   push:
-    branches: [ master ]
+    branches: [master]
   pull_request:
-    branches: [ master ]
+    branches: [master]
 
 # A workflow run is made up of one or more jobs that can run sequentially or in parallel
 jobs:
@@ -29,16 +29,16 @@ jobs:
           # lts/gallium node v19.7.0 (npm v9.5.0)
           node-version: '19.7.0'
       - name: Angular CLI install
-        run : npm install -g --silent @angular/cli@14.2.12
+        run: npm install -g --silent @angular/cli@14.2.12
 
       - name: Npm install
         run: npm install
 
       - name: Run eslint
-        run : npx ng lint
+        run: npx ng lint
 
       - name: Run build
-        run : npm run build:prod
+        run: npm run build:prod
 
       - name: Deploy to github pages
         if: ${{ github.event_name == 'push' }}

.github/workflows/create-docker-hub-image.yml

@@ -1,33 +1,31 @@
-name: Publish Image in Docker Hub 
+name: Publish Image in Docker Hub
 
 on:
   push:
-    branches: [ master ]
+    branches: [master]
 
 jobs:
-
   build:
-  
     runs-on: ubuntu-latest
     env:
-        DOCKER_ORGANIZATION: ${{secrets.DOCKER_ORGANIZATION}}
+      DOCKER_ORGANIZATION: ${{secrets.DOCKER_ORGANIZATION}}
-        WEB_APP_VERSION: ${{secrets.WEB_APP_LATEST_STABLE_VERSION}}
+      WEB_APP_VERSION: ${{secrets.WEB_APP_LATEST_STABLE_VERSION}}
 
     steps:
-    - uses: actions/checkout@v2
+      - uses: actions/checkout@v2
 
-    - name: Docker Hub Login
+      - name: Docker Hub Login
-      env:
+        env:
-        DOCKER_USER: ${{secrets.DOCKER_USER}}
+          DOCKER_USER: ${{secrets.DOCKER_USER}}
-        DOCKER_PASSWORD: ${{secrets.DOCKER_PASSWORD}}
+          DOCKER_PASSWORD: ${{secrets.DOCKER_PASSWORD}}
-      run: |
+        run: |
-        echo $DOCKER_PASSWORD | docker login -u $DOCKER_USER --password-stdin
+          echo $DOCKER_PASSWORD | docker login -u $DOCKER_USER --password-stdin
 
-    - name: Build the Docker image
+      - name: Build the Docker image
-      run: docker build -t web-app:latest .
+        run: docker build -t web-app:latest .
-      
-    - name: Docker Hub Prepare
-      run: docker image tag web-app $DOCKER_ORGANIZATION/web-app:$WEB_APP_VERSION
 
-    - name: Docker Hub Push  
+      - name: Docker Hub Prepare
-      run: docker image push $DOCKER_ORGANIZATION/web-app:$WEB_APP_VERSION
+        run: docker image tag web-app $DOCKER_ORGANIZATION/web-app:$WEB_APP_VERSION
+
+      - name: Docker Hub Push
+        run: docker image push $DOCKER_ORGANIZATION/web-app:$WEB_APP_VERSION

.github/workflows/stale.yml

@@ -4,23 +4,23 @@
 name: Mark stale issues and pull requests
 on:
   schedule:
-  - cron: "0 0 * * *"
+    - cron: '0 0 * * *'
 permissions:
   contents: read
 
 jobs:
   stale:
     permissions:
-      issues: write  # for actions/stale to close stale issues
+      issues: write # for actions/stale to close stale issues
-      pull-requests: write  # for actions/stale to close stale PRs
+      pull-requests: write # for actions/stale to close stale PRs
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/stale@9c1b1c6e115ca2af09755448e0dbba24e5061cc8 # tag=v5
+      - uses: actions/stale@9c1b1c6e115ca2af09755448e0dbba24e5061cc8 # tag=v5
-      with:
+        with:
-        repo-token: ${{ secrets.GITHUB_TOKEN }}
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
-        # stale-issue-message: 'Stale issue message'
+          # stale-issue-message: 'Stale issue message'
-        # stale-issue-label: 'no-issue-activity'
+          # stale-issue-label: 'no-issue-activity'
-        stale-pr-message: 'This pull request seems to be stale.  Are you still planning to work on it?  We will automatically close it in 30 days.'
+          stale-pr-message: 'This pull request seems to be stale.  Are you still planning to work on it?  We will automatically close it in 30 days.'
-        stale-pr-label: 'stale'
+          stale-pr-label: 'stale'
-        days-before-stale: 30
+          days-before-stale: 30
-        days-before-close: 30
+          days-before-close: 30

.prettierignore

@@ -5,4 +5,3 @@
 *.js
 *.json
 *.ts
-*.yml