Epic: Manage CodeQL deployment

[roslynwythe]

Overview

We require issues to support resolution of current open CodeQL alerts as well as automation for creation of issues for new CodeQL alerts. We also need to manage CodeQL extraction errors and consider implementing CodeQL for VS Code extension.

Dependencies

• [ ] #5242
• [ ] #6463
• [ ] #5159
• [x] #5059
• [x] #5234
• [ ] #6548
• [x] #5180
• [x] #6691

Action Items

• [x] View the code scanning page[^1] for hackforla/website, and understand the elements of CodeQL code scanning[^2]
• [x] Create issue template #5242
• [x] Create a sample issue - #5642
• [x] Create a level 1 issue making issue with a list of required issues - see #5159
• [x] Create an issue for creation of a wiki page "How to manage CodeQL alerts" - #6463
• [ ] fix link from Action Item to alert
• [ ] set role label based on path of affected code file
  • [ ] if path starts with .github or github-actions => apply `role: back end/devOps
  • [ ] otherwise apply role: front end label
• [ ] determine if the code file is in production
  • [ ] for pages, check YAML front matter for published:
  • [ ] for layouts, check _config.yml

Resources/Instructions

[^1]: Code Scanning results for hackforla/website [^2]: About code scanning with CodeQL [^3]: spreadsheet HfLA website: CodeQL scan alerts (issue #5060)

• This Epic was created from #4963

[github-actions[bot]]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing: Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards. To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels

[github-actions[bot]]

Hi @roslynwythe, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[ExperimentsInHonesty]

• @roslynwythe There was a dependency on this for #5060 to be done first, but I think the issue template for auditing has to be made first, so that the issues in 5060 can be made. So I have fixed it. If you agree, re add the ready for prioritization label and I will take care of it. If you don't agree, please explain what I might be misunderstanding.

[github-actions[bot]]

Hi @roslynwythe, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[github-actions[bot]]

Hi @roslynwythe, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

[roslynwythe]

Issue 1 (Analysis) Template Draft

(Title) Analysis for CodeQL query [QUERY NAME]

Prerequisite

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 page.
2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

We need to analyze the query [QUERY NAME] which appears in the CodeQL code scan results[^2] and we need to make recommendations about the disposition of each specific alert found from that query. Analysis and Recommendations will be recorded in the spreadsheet: HfLA website: CodeQL scan alerts[^1]

Action Items

• [ ] Open the spreadsheet HfLA website: CodeQL scan alerts[^1] (CodeQL query types sheet) and locate the row in which the Query column contains [QUERY NAME]
• [ ] From the code scanning results page[^2] browse to an alert with query type [QUERY NAME]. Copy the query, severity level, description, and recommendation text from the webpage into a new row in the CodeQL query types sheet.
• [ ] Observe the query tags listed on the right column of the webpage. If the tag security is listed, check the "Security Alert?" column of the spreadsheet.
• [ ] Add your analysis and recommendation
  • [ ] In the "recommended action" column, select from the following: dismiss as test, dismiss as false positive, dismiss as won't fix, change code, or varies by instance
  • [ ] DO NOT DISMISS ANY ALERTS in the code scanning results page[^2]
• [ ] Populate a row in the Alert Instances sheet for each alert instance in the code scanning results page[^2]; Complete the query, link to alert page and file columns
  • [ ] If the recommendation is fix code, populate these columns:
    • [ ] Line of current code
    • [ ] Recommended line of code
    • [ ] web page - URL of the affected web page, for testing purposes
    • [ ] test procedure- describe the process which can be used after the code fix has been made, to check that the change has not broken anything.
• [ ] After all instances have been recorded in the sheet, add the ready for dev lead label to this issue and move it to the Questions/In Review column

For merge team/dev lead

• [ ] To review this issue:
  • [ ] Locate the row in the CodeQL query types sheet. All columns should be populated.
  • [ ] Locate the rows in theAlert Instances. There should be a row for each instance of the alert in the code scanning results page[^2]. For each row:
    • [ ] If the recommendation is change code, all columns must be completed with the exception of Link to Issue
    • [ ] If the recommendation is to dismiss, none of the remaining columns are required (as indicated on the sheet)
• [ ] Review recommendations. If you agree with the recommendation to dismiss the alert, dismiss the alert.
• [ ] Remove the ready for dev lead label and close the issue
• [ ] If new issues are required to make code fixes, put the issue in "New Issue Approval" with "ready for dev lead" label
• [ ] Check off the Issue in #5060

Resources/Instructions

[^1]: spreadsheet: HfLA website: CodeQL scan alerts - issue #5060 [^2]:Code scanning results page

• GitHub CodeQL documentation
• This issue is tracked in the spreadsheet HfLA website: CodeQL scan alerts (issue #5060) and #5060

[roslynwythe]

• @roslynwythe There was a dependency on this for Create Issues for Analysis of CodeQL alerts #5060 to be done first, but I think the issue template for auditing has to be made first, so that the issues in 5060 can be made. So I have fixed it. If you agree, re add the ready for prioritization label and I will take care of it. If you don't agree, please explain what I might be misunderstanding.

• @ExperimentsInHonesty I understand that the template must be made first before the issues can be made, but if you list this Epic as a dependency on #5060. doesn't that imply that this Epic must be closed before work can be begin on #5060? This Epic encompasses both the auditing and the code changes resulting from CodeQL alerts, so I was expecting that it would remain open until all those issues are created or even until they are completed.

• When I setup the dependencies the other way around (listing #5060 as a dependency on this issue), I was attempting to model this issue after other Epics and Roll Out Plans (for example #4362), where I noticed that the lower-level issue-making issues were listed as dependencies on the higher-level issues. At first that logic seemed backward but now I understand it to mean that the higher level issue must remain open until the all the lower level issues are closed.

But I'm ok however we setup the dependencies.

• Also, there are some other requirements related to CodeQL:
  • Issues for managing secret scanning
  • Issues creating email notifications for secret scanning and CodeQL alerts (I believe these may be require GHAs) - #5059
  • ~~An Issue to clarify policy/documentation for reviewing alerts as part of the Pull Request Review process~~

and I'm not sure, should those requirements be incorporated into this Epic?

I would like to remain assigned to this issue.

Thank you

[roslynwythe]

Issue 2 (Code Fix) Template Draft

(Title) Code Change for resolve CodeQL alert

Prerequisite

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 page.
2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

We need to make a code change in order to resolve a CodeQL alert [LINK TO ALERT PAGE]

Action Items

• [ ] Open the file [FILE PATH] in your IDE
• [ ] Replace the line

[REPLACE WITH EXISTING LINE OF CODE]

with

[REPLACE WITH DESIRED LINE OF CODE]

• [ ] Using docker, browse to [WEB PAGE]. [TEST PROCEDURE]

For merge team/dev lead

• [ ] Check off the Issue in #5159

Resources/Instructions

• Code scanning results page
• This issue is part of #5159

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, August 15, 2023 at 12:05 AM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, August 29, 2023 at 12:06 AM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, September 5, 2023 at 12:05 AM PST.}

[roslynwythe]

Issue 1 (analysis) template

### Prerequisite
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 page](https://www.hackforla.org/getting-started).
2. Before you claim or start working on an issue, please make sure you have read our [How to Contribute to Hack for LA Guide](https://github.com/hackforla/website/blob/7f0c132c96f71230b8935759e1f8711ccb340c0f/CONTRIBUTING.md).

### Overview
We need to analyze the query type `Potentially unsafe external link` which appears in the CodeQL code scan results on the hackforla/website repository, and to make recommendations about the disposition of each specific alert found with that query.  Analysis and Recommendations will be recorded in the spreadsheet: **HfLA website: CodeQL scan alerts[^1]

### Action Items
- [x] Open the spreadsheet HfLA website: CodeQL scan alerts[^1]
- [x] From the **code scanning results page**[^2] browse to an alert with query type `Potentially unsafe external link`.  Copy the query, severity level, description, and recommendation text from the webpage into a new row in the spreadsheet. 
- [x] Observe the query tags listed on the left column of the webpage.  If the tag `security` is listed, check the "Security Alert?" column of the spreadsheet.  
- [x] Add your analysis and recommendation
   - [x] In the "recommended action" column, select from the following: `dismiss as test`, `dismiss as false positive`, `dismiss as won't fix`, `fix code`, or `varies by instance`
   - [x] If the recommendation is `fix code`, describe the code change in the `recommended code change` column
- [x] Populate a row in the `Specific Alert Instances` sheet for each alert instance, by completing the `query`, `alert #` and `file` columns  
- [x] If the recommndation is `fix code`, populate these columns:
  - [x]  `original code`
  - [x]  `recommended code change`
  - [x] `web page` - URL of the affected web page, for testing purposes
  - [x] `test procedure`- describe the process which can be used after the code fix has been made, to check that the change has not broken anything.    
- [x] After all instances have been recorded in the sheet, add the `ready for dev lead` label to this issue and move it to the `Questions/In Review column`

### For merge team/dev lead
- [x] After reviewing the issue
   - [x] If the recommendation is to dismiss one or more alerts, go to the **code scanning results page**[^2] page and dismiss each specific alert using the specified message. 
   - [x] Remove the `ready for dev lead` label and close the issue
   - [x] Check off the Issue in #5060
  
### Resources/Instructions
[^1]: spreadsheet: [HfLA website: CodeQL scan alerts](https://docs.google.com/spreadsheets/d/1B3R-fI8OW0LcYuwZICQZ2fB8sjlE3VsfyGIXoReNBIs/edit#gid=193401043)
[^2]:[Code scanning results page](https://github.com/hackforla/website/security/code-scanning)

- [GitHub CodeQL documentation](https://codeql.github.com/docs/codeql-overview/about-codeql/)
- This issue is tracked in the spreadsheet [HfLA website: CodeQL scan alerts](https://docs.google.com/spreadsheets/d/1B3R-fI8OW0LcYuwZICQZ2fB8sjlE3VsfyGIXoReNBIs/edit#gid=193401043) and #5060

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Tuesday, September 19, 2023 at 12:06 AM PST.}

[roslynwythe]

Template for Analysis for CodeQL alerts detected within Pull Requests

Prerequisite

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 page.
2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

We need to analyze the CodeQL alert of type [QUERY NAME] detected in the file [FILE] in Pull Request [PULL REQUEST] and we need to make recommendations about the disposition of the alert. Analysis and Recommendations will be recorded in the spreadsheet: HfLA website: CodeQL scan alerts[^1]

Action Items

• [ ] Browse to the Pull Request #[PULL REQUEST NUMBER] and locate the code annotation describing the alert. Browse to the alert details page (link labelled "show more details")
• [ ] Open the spreadsheet HfLA website: CodeQL scan alerts[^1] (CodeQL query types sheet) and locate any rows in which the Query column contains [QUERY NAME]. If a row exists, read and understand the previous handling of similar alerts. If a row does not exist, create a new row, then copy the query, severity level, description, and recommendation text from the webpage into a new row in the CodeQL query types sheet.
• [ ] Observe the query tags listed on the right column of the webpage. If the tag security is listed, check the "Security Alert?" column of the spreadsheet.
• [ ] Add your analysis and recommendation
  • [ ] In the "recommended action" column, ?????? select from the following: dismiss as test, dismiss as false positive, dismiss as won't fix, change code, or varies by instance
  • [ ] DO NOT DISMISS ANY ALERTS in the code scanning results page[^2]
• [ ] Populate a row in the Alert Instances sheet; Complete the query, link to alert page and file columns
  • [ ] If the recommendation is fix code, populate these columns:
    • [ ] Line of current code
    • [ ] Recommended line of code
    • [ ] web page - URL of the affected web page, for testing purposes
    • [ ] test procedure- describe the process which can be used after the code fix has been made, to check that the change has not broken anything.
• [ ] After all instances have been recorded in the sheet, add the ready for dev lead label to this issue and move it to the Questions/In Review column

For merge team/dev lead

• [ ] To review this issue:
  • [ ] Locate the row in the CodeQL query types sheet. All columns should be populated.
  • [ ] Locate the rows in theAlert Instances. There should be a row for each instance of the alert in the code scanning results page[^2]. For each row:
    • [ ] If the recommendation is change code, all columns must be completed with the exception of Link to Issue
    • [ ] If the recommendation is to dismiss, none of the remaining columns are required (as indicated on the sheet)
• [ ] Review recommendations. If you agree with the recommendation to dismiss the alert, dismiss the alert.
• [ ] Remove the ready for dev lead label and close the issue
• [ ] If new issues are required to make code fixes, put the issue in "New Issue Approval" with "ready for dev lead" label
• [ ] Check off the Issue in #5060

Resources/Instructions

[^1]: spreadsheet: HfLA website: CodeQL scan alerts - issue #5060 [^2]:Code scanning results page

• GitHub CodeQL documentation
• This issue is tracked in the spreadsheet HfLA website: CodeQL scan alerts (issue #5060) and #5060

[roslynwythe]

(Title) Analysis for CodeQL alert [ALERT #]

Prerequisite

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 page.
2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

We need to analyze CodeQL query alert {INSERT ALERT #} and to recommend appropriate disposition of the alert. Options include dismissal of the alert or code fix; recommendations will be recorded in the spreadsheet: HfLA website: CodeQL scan alerts[^3]

Action Items

• [ ] Open the spreadsheet HfLA website: CodeQL scan alerts[^1] and locate the row for alert # [ALERT #]
• [ ] Browse to the alert url[^2]. Note the severity level from the webpage and set the severity level column of the spreadsheet accordingly.
• [ ] Observe the query tags listed on the right column of the webpage. If the tag security is listed, check the "Security Alert?" column of the spreadsheet.
• [ ] Add your analysis and recommendation
  • [ ] In the "recommended action" column, select from the following: dismiss as test, dismiss as false positive, dismiss as won't fix, or change code
  • [ ] DO NOT DISMISS ANY ALERTS. Dismissal of alerts should be done by merge team only after review of this issue.
• [ ] Complete the query, link to alert page and file columns
  • [ ] If the recommendation is fix code, populate these columns:
    • [ ] Line of current code
    • [ ] Recommended line of code
    • [ ] web page - URL of the affected web page, for testing purposes
    • [ ] test procedure- describe the process which can be used after the code fix has been made, to check that the change has not broken anything.
• [ ] Add the ready for dev lead label to this issue and move it to the Questions/In Review column

For merge team/dev lead

• [ ] To review this issue:
  • [ ] Locate the row in the CodeQL query types sheet.
    • [ ] If the recommendation is change code, all columns must be completed with the exception of Link to Issue
    • [ ] If the recommendation is to dismiss, none of the remaining columns are required (as indicated on the sheet)
• [ ] Review recommendations. If you agree with the recommendation to dismiss the alert, dismiss the alert.
• [ ] Remove the ready for dev lead label and close the issue
• [ ] If new issues are required to make code fixes, put the issue in "New Issue Approval" with "ready for dev lead" label
• [ ] Check off the Issue in #5060

Resources/Instructions

[^1]: spreadsheet: HfLA website: CodeQL scan alerts - issue #5060 [^2]:CodeQL query alert {INSERT ALERT #}

• GitHub CodeQL documentation
• This issue is tracked in the spreadsheet HfLA website: CodeQL scan alerts (issue #5060) and #5060

[roslynwythe]

Revised issue template - note that there are 3 instances of 'INSERT-ALERTID' below

Title: Resolve CodeQL Alert INSERT-ALERTID: Recommend dismissal or update code

Prerequisite

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 page.
2. Before you claim or start working on an issue, please make sure you have read our How to Contribute to Hack for LA Guide.

Overview

As developers. we need to analyze CodeQL query alert INSERT-ALERTID and to either recommend dismissal of the alert or update the code to resolve the alert.

Action Items

• [ ] DO NOT DISMISS ANY ALERTS. Dismissal of alerts should be done by dev leads only after review of the recommendation
• [ ] Browse to the link in the next Action Item and read the contents. Click "See More" to view Recommendations, Examples and References.
• [ ] https://github.com/hackforla/website/security/code-scanning/INSERT-ALERTID
• [ ] In a comment in this issue, add your analysis and recommendations with details. The recommendation can be one of the following: dismiss as test, dismiss as false positive, dismiss as won't fix, or update code. An example of a 'false positive' is a report of a JavaScript syntax error that is caused by markdown or liquid symbols such as --- or {%.
• [ ] If the recommendation is to update code:
  • [ ] create an issue branch and proceed with the code update
  • [ ] Use docker to test locally, ensuring that there are no changes to any affected webpage(s)
  • [ ] proceed with pull request in the usual manner
• [ ] If the recommendation is to dismiss, describe your reason for dismissal in the comment, then move the issue to Questions/In Review and apply the label ready for dev lead.

For merge team/dev lead

• [ ] If recommendation to dismiss is approved, dismiss the alert with a comment, then close the issue as completed.
• [ ] When this issue is closed please check off the dependency (under "Analysis Issues") in #5005. If all analysis issues are closed, close #5005 as completed.

Resources/Instructions

• GitHub CodeQL documentation
• This issue is part of #5005

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, December 4, 2023 at 11:06 PM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, December 11, 2023 at 11:06 PM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, December 18, 2023 at 11:06 PM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, December 25, 2023 at 11:06 PM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, January 1, 2024 at 11:06 PM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, January 8, 2024 at 11:05 PM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, January 15, 2024 at 11:06 PM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, January 22, 2024 at 11:05 PM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, January 29, 2024 at 11:06 PM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, February 5, 2024 at 11:06 PM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, February 12, 2024 at 11:05 PM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, February 19, 2024 at 11:06 PM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, February 26, 2024 at 11:06 PM PST.}

[github-actions[bot]]

@roslynwythe

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

_{You are receiving this comment because your last comment was before Monday, March 4, 2024 at 11:06 PM PST.}