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

Update spell-check-audit.md label and issue template #7713

Merged
merged 2 commits into from
Nov 18, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/ISSUE_TEMPLATE/spell-check-audit.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
name: Spell check audit web page
about: For checking spelling on a code file that contains text displayed on the website
title: Run VS Code Spell Checker on [INSERT FILE HERE]
labels: 'Complexity: Small, feature: spelling, ready for dev lead, role: back end/devOps,
labels: 'Complexity: Small, feature: spelling, ready for merge team, role: back end/devOps,
role: front end, size: 0.5pt'
assignees: ''

Expand All @@ -18,7 +18,7 @@ We need to audit HfLA codebase files for spelling errors using the Code Spell Ch
- [ ] Locate the file in column A ("File") of the "Page Audit" sheet. In the column labeled "Result Summary", select the appropriate option: `No errors` or `At least one error`.
- [ ] If at least one error was reported, copy/paste each cSpell message into a separate row in the `Results` sheet
- [ ] In each new row, select the appropriate value: `misspelling` or `false positive` from the "Result type" column. A false positive is a term that is not a misspelling but is not recognized by the spell checker because it is a technical term, abbreviation, acronym, URL or proper noun (name of a person, place or organization).
- [ ] Move this issue to the Questions/In Review column and apply the label `ready for dev lead`
- [ ] Move this issue to the Questions/In Review column and apply the label `ready for merge team`

### Merge Team
- [ ] After this issue is closed, release the dependency on this issue in #5248
Expand Down