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 119-125 of spreadsheet #6872

Open
10 tasks
roslynwythe opened this issue May 21, 2024 · 2 comments
Open
10 tasks

Create spellcheck audit issues from line 119-125 of spreadsheet #6872

roslynwythe opened this issue May 21, 2024 · 2 comments
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: back end role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less
Milestone

Comments

@roslynwythe
Copy link
Member

roslynwythe commented May 21, 2024

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 spreadsheet1

Action Items

  • For each line 119-125 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 dev lead"

Note for Dev Leads after issue signoff

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 May 21, 2024
@HackforLABot HackforLABot added this to New Issue Approval in Project Board May 21, 2024

This comment was marked as outdated.

@roslynwythe roslynwythe added role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 0.5pt Can be done in 3 hours or less epic Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level feature: spelling 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 May 21, 2024
@ExperimentsInHonesty ExperimentsInHonesty added this to the 05. Know HFLA milestone May 26, 2024
@ExperimentsInHonesty

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Ready for Prioritization labels May 26, 2024
@roslynwythe roslynwythe added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels May 28, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Approval to ERs and epics that are ready to be turned into issues in Project Board Jun 2, 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: back end 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
Project Board
  
ERs and epics that are ready to be tu...
Development

No branches or pull requests

2 participants