Check pr

.github/ISSUE_TEMPLATE/add-github-handle.md

@@ -2,8 +2,9 @@
 name: github-handle in project file
 about: For adding github-handle to member data in a project file
 title: Add github-handle for [INSERT NAME] in [INSERT PROJECT FILE]
-labels: 'good first issue, P-Feature: Project Info and Page, ready for dev lead, role:
-  back end/devOps, role: front end, size: 0.25pt'
+labels: 'Complexity: Small, feature: spelling, good first issue, P-Feature: Project
+  Info and Page, ready for dev lead, role: back end/devOps, role: front end, size:
+  0.5pt, size: 0.25pt'
 assignees: ''
 
 ---

.github/ISSUE_TEMPLATE/communities-of-practice-information-updates.yml

@@ -71,11 +71,10 @@ body:
         Title:
         GitHub Handle:
         Slack Member ID:
-  - type: markdown
-    attributes:
-      value: "### Resources"
   - type: markdown
     attributes:
       value: |
-        folder where files are in the repo: https://github.com/hackforla/website/tree/gh-pages/_data/internal/communities
-        where you can see the live page: https://www.hackforla.org/communities-of-practice
+        ### Resources
+        * Folder where files are in the repo: https://github.com/hackforla/website/tree/gh-pages/_data/internal/communities
+        * Where you can see the live page: https://www.hackforla.org/communities-of-practice
+        * If you need to update your meeting times, names, dates, or frequency, please see the [VRMS User Guide](https://github.com/hackforla/VRMS/wiki/User-Guide). The HackforLA.org website gets the meeting times from the updates made to each Community of Practice's meeting data in vrms.io

.github/ISSUE_TEMPLATE/pre-work-template---design.md

@@ -26,7 +26,7 @@ As a new designer on the HfLA website UX team, fill in the following fields as y
 - [ ] Attend weekly team meetings: 
    - [ ] UX weekly team meeting, Wednesday 2:30 pm PST
    - [ ] All team meeting (UX, Development, Product), Sunday 10am PST
- - [ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Wednesdays and Sundays). In case, you are unable in any given week, you should reach out to the design lead. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the design lead know (through a slack message in the hfla-site channel as well as an @ mention in a comment of the issue that you would be working on) if you are planning to take a week off or a longer vacation.
+ - [ ] Note regarding weekly team meeting requirements: All website team members are required to attend at least 1 team meeting in a week (held on Wednesdays and Sundays). In case, you are unable in any given week, you should reach out to the design lead. Exceptions to this requirement may be provided on a case-by-case basis. Also, please let the design lead know (through a Slack message in the hfla-site channel as well as an @ mention in a comment of the issue that you would be working on) if you are planning to take a week off or a longer vacation.
 - [ ] Review [Design_Short Term Goals, Plan, and Tasks](https://docs.google.com/document/d/1FxwgdnWBbbQ8Pi3tspnukZTWwXtqnRXfNkNhVMEloY0/edit)
 - [ ] Review the [Start Here](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=8561%3A72465) and [Design System](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=3464%3A3) pages in Figma
 - [ ] Review the [prioritized Backlog to see what Design Issues](https://github.com/hackforla/website/projects/7?card_filter_query=label%3A%22role%3A+design%22#column-7198257) are available (this will not be the complete list, but will give you some talking points for your conversation with your lead).

.github/ISSUE_TEMPLATE/project-profile-leader-updates---add.md

@@ -0,0 +1,44 @@
+---
+name: Project Profile leader updates - Add
+about: This template is for website team only to ADD a single volunteer
+title: 'Update Project Profile: [Project Name] Add [Name of Volunteer]'
+labels: 'good first issue, P-Feature: Project Info and Page, role: back end/devOps,
+  role: front end, size: 0.25pt, time sensitive'
+assignees: ''
+
+---
+
+### Prerequisites
+1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our [Getting Started](https://www.hackforla.org/getting-started) page and attend an onboarding session.
+2. You have already read our [How to Contribute to Hack for LA Guide](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md).
+
+### Overview
+We need to keep project information up to date so that visitors to the website can find accurate information.
+
+### Action Items
+- [ ] In your IDE, open the `_projects/[Insert filename].md` file.
+- [ ] Observe the existing syntax of the front matter block [^1] in the file.
+- [ ] Find the `leadership` variable and add the following profile. 
+```
+  - name: [Insert leadership member's name]
+    github-handle: [Insert GitHub handle]
+    role: [Insert role]
+    links:
+      slack: https://hackforla.slack.com/team/[Insert Slack member ID]
+      github: https://github.com/[Insert GitHub handle]
+    picture: https://avatars.githubusercontent.com/[Insert GitHub handle]
+```
+- [ ] Verify the changes by viewing the following in your local environment and include before and after screenshots with your pull request:
+  - [ ] [Insert name of project] page [^2]
+- [ ] Once your pull request is merged, go to the initiating ER [^3]
+  - [ ] Check off this issue under the _Dependency_ section
+  - [ ] If all the issues in the _Dependency_ section are checked off, move initiating ER [^3] to **Questions / In Review** column and uncheck the **Dependency label**.
+    - <details>
+        <summary>Click here to see how to uncheck the <b>Dependency label</b></summary>
+        <img src="https://github.com/hackforla/website/assets/31293603/6f53f4d4-7d2c-45f8-8534-9936fc9adee8" width="300px">
+      </details>
+
+### Resources/Instructions
+[^1]: [Info about the front matter block](https://jekyllrb.com/docs/front-matter/)
+[^2]: Project detailed info page URL: [Insert project specific page URL here]
+[^3]: initiating ER:  #[Insert ER number]

.github/ISSUE_TEMPLATE/project-profile-leader-updates---remove.md

@@ -0,0 +1,38 @@
+---
+name: Project Profile leader updates - Remove
+about: 'This template is for website team only to REMOVE a single volunteer '
+title: 'Update Project Profile: [Name of Project] Remove [Name of Volunteer]'
+labels: 'good first issue, P-Feature: Project Info and Page, role: back end/devOps,
+  role: front end, size: 0.25pt, time sensitive'
+assignees: ''
+
+---
+
+### Prerequisites
+1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our [Getting Started](https://www.hackforla.org/getting-started) page and attend an onboarding session.
+2. You have already read our [How to Contribute to Hack for LA Guide](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md).
+
+### Overview
+We need to keep project information up to date so that visitors to the website can find accurate information.
+
+### Action Items
+- [ ] In your IDE, open the `_projects/[Insert filename].md` file.
+- [ ] Observe the existing syntax of the front matter block [^1] in the file.
+- [ ]  Find the `leadership` variable and remove the following:
+```
+[Insert the lines of code to remove the specified leadership member]
+```
+- [ ] Verify the changes by viewing the following in your local environment and include before and after screenshots with your pull request:
+  - [ ] [Insert name of project] page [^2]
+- [ ] Once your pull request is merged, go to the initiating ER [^3]
+  - [ ] Check off this issue under the _Dependency_ section
+  - [ ] If all the issues in the _Dependency_ section are checked off, move initiating ER [^3] to **Questions / In Review** column and uncheck the **Dependency label**.
+    - <details>
+        <summary>Click here to see how to uncheck the <b>Dependency label</b></summary>
+        <img src="https://github.com/hackforla/website/assets/31293603/6f53f4d4-7d2c-45f8-8534-9936fc9adee8" width="300px">
+      </details>
+
+### Resources/Instructions
+[^1]: [Info about the front matter block](https://jekyllrb.com/docs/front-matter/)
+[^2]: Project detailed info page URL: [Insert project specific page URL here]
+[^3]: initiating ER:  #[Insert ER number]

.github/workflows/move-closed-issues.yaml

@@ -3,24 +3,31 @@ on:
   issues:
     types:
       - closed
-      
+
 jobs:
   Move-Closed-Issues:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
+
+      # 1: Sort closed issues based on labels
       - name: Sort Closed Issues by Label
         uses: actions/github-script@v7
         id: sort-closed-issues
         with:
           script: |
-            const script = require('./github-actions/move-closed-issues/sort-closed-issues.js')
-            const sortIssues = script({context})
-            return sortIssues
+            const script = require('./github-actions/move-closed-issues/sort-closed-issues.js');
+            const sortIssues = script({context});
+            return sortIssues;
           result-encoding: string
-
-      # Post-migration to Projects Beta:
-      # Move-Closed-Issues to "QA" column by default; OR move to "Done" based on `sort-closed-issues.js`
-      - name: Move Closed Issues
-        run: echo "Based on its labels, issue should be sorted to 'status' of '${{ steps.sort-closed-issues.outputs.result }}'" 
-
+
+      # 2: Move closed issues
+      - name: Move Closed Issue
+        uses: actions/github-script@v7
+        id: move-closed-issue
+        with:
+          github-token: ${{ secrets.HACKFORLA_GRAPHQL_TOKEN }}
+          script: |
+            const results = '${{ steps.sort-closed-issues.outputs.result }}';
+            const script = require('./github-actions/move-closed-issues/move-closed-issues.js');
+            script({github, context}, results);

.github/workflows/schedule-fri-0700.yml

@@ -12,11 +12,8 @@ jobs:
     steps:
       - uses: actions/checkout@v4
       - uses: actions/github-script@v7
-        env:
-          HACKFORLA_ADMIN_TOKEN: ${{ secrets.HACKFORLA_ADMIN_TOKEN }}
         with:
-          github-token: ${{ secrets.HACKFORLA_GRAPHQL_TOKEN }}  
+          github-token: ${{ secrets.HACKFORLA_GRAPHQL_TOKEN }}
           script: |
-            const HACKFORLA_ADMIN_TOKEN = process.env.HACKFORLA_ADMIN_TOKEN;
             const script = require('./github-actions/trigger-schedule/add-update-label-weekly/add-label.js');
-            script({ g: github, c: context }, HACKFORLA_ADMIN_TOKEN);
+            script({ g: github, c: context });

.github/workflows/update-label-directory.yml

@@ -0,0 +1,50 @@
+# This workflow updates `github-actions/utils/_data/label-directory.json`
+# and the Google Sheets doc `Website Labels 'Source of Truth'` at URL below
+
+name: Update Label Directory
+
+on:
+  label:
+    types: [edited, created, deleted]
+
+jobs:
+  Update-Label-Directory:
+    runs-on: ubuntu-latest
+    if: github.repository == 'hackforla/website'
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          token: ${{ secrets.HACKFORLA_BOT_PA_TOKEN }}
+
+      - name: Update label directory
+        id: update-label-directory
+        uses: actions/github-script@v7
+        with:
+          github-token: ${{ secrets.HACKFORLA_BOT_PA_TOKEN }}
+          script: |
+            const script = require('./github-actions/utils/update-label-directory.js')
+            const labelPacket = script({g: github, c: context})
+            return labelPacket
+
+      # NOTE: the the URL below matches the **current deployment URL** of the Apps Script
+      # associated with the 'Source of Truth'Label spreadsheet and maintained by
+      # `[email protected]`. (If something is broken, check this link first)
+      - name: Send POST request to Google Apps Script
+        env:
+          label_edits: ${{ steps.update-label-directory.outputs.result }}
+        run: |
+          curl -X POST "https://script.google.com/macros/s/AKfycbw_rM8kwRea_iT6NbP1k5c7nJl5qg-5IwiTPXUyd7V2Oe_TN_TbapdpcVtLPHieKdUt/exec" \
+           -H "Content-Type: application/json" \
+           -d "$label_edits"
+
+      # Before next step, run `git pull` so that branch is current
+      - name: Pull latest changes from gh-pages
+        run: git pull
+
+      - name: Commit changes to JSON Label Directory
+        uses: stefanzweifel/[email protected]
+        with:
+          # Glob pattern of file to commit, and opt. commit message + author
+          file_pattern: github-actions/utils/_data/label-directory.json
+          commit_message: Update label directory
+          commit_author: GitHub Actions Bot <[email protected]>