Create spellcheck audit issues from line 119-125 of spreadsheet

[roslynwythe]

Overview

We need to create issues for the spellcheck audit. The filepaths for the required issues are found in lines 119-125 of the HfLA spelling audit spreadsheet¹

Action Items

• For each line 119-125 in the HfLA spelling audit spreadsheet¹
  • Copy the filepath (for example pages/toolkit.html) from column A then create a new issue using the "Spell check audit web page template"²
  • Replace the text [INSERT FILE HERE] with the filename (for example toolkit.html)
  • Replace the text [INSERT FILE PATH] with the full file path (for example pages/toolkit.html)
  • Click "Submit New Issue"
  • Copy the issue number and use it to create a link below under "Child Issues that this issue creates" (for example if you enter - [ ] #6497, GitHub will expand that into an issue link
  • Copy the issue number and paste it into the "Link to Audit Issue" column in the spreadsheet in the row that corresponds to the filepath
• When all issues have been created, move this issue into the "Questions/In Review" column and add the label "ready for merge team"

Note for Dev Leads after issue sign-off

• Add all the issues created by this issue to the Epic Epic: Create template, spreadsheet and list of issues for spellcheck audit #5248

Resources/Instructions

• This issue is part of Epic: Create template, spreadsheet and list of issues for spellcheck audit #5248

Child Issues that this issue creates

• Run VS Code Spell Checker on 100-automations.md #7609
• Run VS Code Spell Checker on 311-data.md #7610
• Run VS Code Spell Checker on access-the-data.md #7611
• Run VS Code Spell Checker on adopt-civic-art.md #7612
• Run VS Code Spell Checker on ballot-nav.md #7613

Footnotes

1. HfLA spelling audit spreadsheet ↩ ↩²

2. Spell check audit web page issue template ↩

[terrencejihoonjung]

Availability: Mon - Fri, 5pm - 9pm PST
ETA: October 13th, 2024, 11:59pm PST

[HackforLABot]

@terrencejihoonjung

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, October 15, 2024 at 12:04 AM PST.}

[terrencejihoonjung]

Progress: Haven't started due to unexpected responsibilities this week but will finish this weekend!
Blockers: N/A
Availability: Fri-Sun 5pm - 10pm PST
ETA: 10/19/24, 11:59pm PST

[terrencejihoonjung]

Progress: Haven't started due to unexpected responsibilities this week but will finish this weekend!
Blockers: N/A
Availability: Fri-Sun 5pm - 10pm PST
ETA: 10/20/24, 11:59pm PST

[terrencejihoonjung]

Hi @roslynwythe

I noticed that issues were already created for filepaths on lines 119 and 120 in the spreadsheet. I created an issue for line 119 before realizing this and did not create one for line 120. Should I ignore lines 119 and 120?

For your reference, here is the (accidentally) created issue for line 119: #7608

Thank you!

[daras-cu]

Hi @terrencejihoonjung, it looks like you're right about there already being issues for those lines in the spreadsheet. There must have been some overlap with a previous issue, thank you for catching that. You can close the issue you created for 119 and disregard 120, then this should be ready for approval.

[terrencejihoonjung]

Hi @daras-cu,

Thanks for the clarification! I went ahead and closed the issue.