Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create spellcheck audit issues from line 143 - 149 of spreadsheet #7587

Open
10 tasks
Tracked by #5248
roslynwythe opened this issue Oct 13, 2024 · 1 comment
Open
10 tasks
Tracked by #5248
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Complexity: Small Take this type of issues after the successful merge of your second good first issue epic feature: spelling Issue Making: Level 1 Make issues from a template and a spreadsheet role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Oct 13, 2024

Overview

We need to create issues for the spellcheck audit. The filepaths for the required issues are found in lines 143 - 149 of the HfLA spelling audit spreadsheet1

Action Items

  • For each line 143 - 149 in the HfLA spelling audit spreadsheet1
    • Copy the filepath (for example pages/toolkit.html) from column A then create a new issue using the "Spell check audit web page template"2
    • 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

Resources/Instructions

Child Issues that this issue creates

  • #

Footnotes

  1. HfLA spelling audit spreadsheet 2

  2. Spell check audit web page issue template

@roslynwythe roslynwythe added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Oct 13, 2024

This comment was marked as outdated.

@roslynwythe roslynwythe added Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Complexity: Small Take this type of issues after the successful merge of your second good first issue epic feature: spelling role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers size: 0.5pt Can be done in 3 hours or less Issue Making: Level 1 Make issues from a template and a spreadsheet Ready for Prioritization and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Oct 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Complexity: Small Take this type of issues after the successful merge of your second good first issue epic feature: spelling Issue Making: Level 1 Make issues from a template and a spreadsheet role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less
Projects
Status: ERs and epics that are ready to be turned into issues
Development

No branches or pull requests

2 participants