-
-
Notifications
You must be signed in to change notification settings - Fork 777
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
Epic: Create Issues to Fix HTML linter errors #5279
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Template "Refactor HTML to resolve linter error"Prerequisite
OverviewWe want to update an HTML tag to resolve the linter error "[REPLACE WITH LINTER ERROR MESSAGE]" Action Items
to
Merge Team
Resources/Instructions
|
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, November 6, 2023 at 11:05 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, November 13, 2023 at 11:06 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, November 20, 2023 at 11:06 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, November 27, 2023 at 11:06 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, December 4, 2023 at 11:06 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, December 11, 2023 at 11:06 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, December 18, 2023 at 11:06 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, December 25, 2023 at 11:06 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, January 1, 2024 at 11:06 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, January 8, 2024 at 11:05 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, January 15, 2024 at 11:06 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, January 22, 2024 at 11:05 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, January 29, 2024 at 11:06 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, February 5, 2024 at 11:06 PM PST. |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, February 12, 2024 at 11:05 PM PST. |
@roslynwythe , @LRenDO has confirmed that there are two open issues that were not listed in the epic here, and are now added |
Hi @freaky4wrld and @roslynwythe! I did a search for open issues "Refactor HTML" that may have been missed or not listed yet in the epic and there are two that are still open. I have added them to the list. |
@LRenDO thanks for clearing out, should I delete the comment? |
Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, February 19, 2024 at 11:06 PM PST. |
@freaky4wrld I would just add an edit note in the comment if you want to update it. |
Please check #6409 which fixes this issue. |
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.
If you need help, be sure to either: 1) place your issue in the You are receiving this comment because your last comment was before Monday, March 4, 2024 at 11:06 PM PST. |
Hi @roslynwythe FYI it appears that the final issue of this epic is merged. |
@roslynwythe Closing this as 'Completed' |
Overview
As developers we need to update HTML markup to address HTML linter errors as recorded in the HfLA HTML linter audit spreadsheet1
Issues to fix HTML linter errors
Action Items
Resources/Instructions
Footnotes
HfLA-Website: HTML linter audit spreadsheet ↩ ↩2
The text was updated successfully, but these errors were encountered: