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 issue template "Resolve Spell Check warning" #6446

Open
1 of 5 tasks
Tracked by #5202 ...
roslynwythe opened this issue Mar 10, 2024 · 7 comments
Open
1 of 5 tasks
Tracked by #5202 ...

Create issue template "Resolve Spell Check warning" #6446

roslynwythe opened this issue Mar 10, 2024 · 7 comments
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Dependency An issue is blocking the completion or starting of another issue feature: spelling ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers size: 0.5pt Can be done in 3 hours or less

Comments

@roslynwythe
Copy link
Member

roslynwythe commented Mar 10, 2024

Dependency

Overview

We need a template for reporting spell check warnings, so that we can create issues to address.

Action Items

  • Create a new file .github/ISSUE_TEMPLATE/spellcheck-warning.md
  • Copy/Paste the text below into the file, then save it
  • Refer to the instructions for testing the new template and preparing the Pull Request. 1

Content of issue template

---
name: Resolve spell check warning
about: For reporting spell check warnings ("unknown word")
title: 'Resolve spell check warning(s) in: [replace with file path] '
labels: 'good first issue, feature: spelling, role: back end/devOps , size: 0.25pt'
assignees: ''

---

### Overview
We need to manage the warnings ("unknown word") generated by spell check

### Action Items
- [ ] Open the file `[REPLACE WITH FILE PATH]` in your IDE
- [ ] Refer to instructions on "How to manage spell check warnings" (resource 1)
- [ ] Copy the block "Resolving spell check warnings" into a new comment in this issue, then select the green Comment button to create the comment. Follow the instructions in the comment you just created.

### Resources/Instructions
1. [draft: How to manage spell check warnings](https://github.com/hackforla/website/issues/6519#issuecomment-2021279777)
2. [Code Spell Checker](https://streetsidesoftware.com/vscode-spell-checker/)
3. [Introduction to JSON](https://www.json.org/json-en.html)
---

Resources

Footnotes

  1. Testing issue templates instructions

@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 Draft Issue is still in the process of being created labels Mar 10, 2024
@github-actions github-actions bot removed the Draft Issue is still in the process of being created label Mar 10, 2024

This comment has been minimized.

@roslynwythe roslynwythe added the Draft Issue is still in the process of being created label Mar 10, 2024
@roslynwythe roslynwythe self-assigned this Mar 10, 2024
@roslynwythe roslynwythe added Complexity: Medium size: 0.5pt Can be done in 3 hours or less Complexity: Small Take this type of issues after the successful merge of your second good first issue role: back end/devOps Tasks for back-end developers feature: spelling Ready for Prioritization and removed Complexity: Medium Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing Draft Issue is still in the process of being created labels Mar 11, 2024
@roslynwythe

This comment was marked as resolved.

@ExperimentsInHonesty

This comment was marked as resolved.

@ExperimentsInHonesty

This comment was marked as resolved.

@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 Mar 24, 2024
@roslynwythe roslynwythe added the Draft Issue is still in the process of being created label Mar 26, 2024
@roslynwythe

This comment was marked as resolved.

@roslynwythe roslynwythe added Dependency An issue is blocking the completion or starting of another issue and removed ready for dev lead Issues that tech leads or merge team members need to follow up on Draft Issue is still in the process of being created labels Mar 26, 2024
@github-actions github-actions bot added the 2 weeks inactive An issue that has not been updated by an assignee for two weeks label Aug 2, 2024

This comment was marked as outdated.

This comment was marked as off-topic.

@ExperimentsInHonesty ExperimentsInHonesty removed Dependency An issue is blocking the completion or starting of another issue 2 weeks inactive An issue that has not been updated by an assignee for two weeks labels Oct 6, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from Ice box to New Issue Approval in P: HfLA Website: Project Board Oct 6, 2024
@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on Added to dev/pm agenda and removed manual dependency release Added to dev/pm agenda labels Oct 6, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Approval to Ice box in P: HfLA Website: Project Board Oct 15, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the Dependency An issue is blocking the completion or starting of another issue label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Dependency An issue is blocking the completion or starting of another issue feature: spelling ready for dev lead Issues that tech leads or merge team members need to follow up on role: back end/devOps Tasks for back-end developers size: 0.5pt Can be done in 3 hours or less
Projects
Development

No branches or pull requests

2 participants