Broken Links QA Parent
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 200
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 5
Description
## User Story
In order to ensure our site remains up to date, datagovteam runs a weekly broken links report in several repos.
As an optional O&M task, create subtasks or attach PRs to this Parent issue that address any cleanup of these broken links, or ignoring of false positives.
The Broken Links reports live in an issue in each repo where the report runs:
| Site | Issue |
| - | - |
| resources.data.gov | https://github.com/GSA/resources.data.gov/issues/811 |
| strategy.data.gov | https://github.com/GSA/data-strategy/issues/338 |
| data.gov 11ty | https://github.com/GSA/datagov-11ty/issues/423 |
| sdg.data.gov | https://github.com/GSA/sdg-indicators-usa/issues/1140 |
## Background
[Any helpful contextual notes or links to artifacts/evidence, if needed]
## Security Considerations ([required](https://nvd.nist.gov/800-53/Rev4/control/CM-4))
[comment]: # "Our SSP says 'The Data.gov team ensures security implications are considered as part of the agile requirements refinement process by including a section in the issue template used as a basis for new work.' so please don't remove this section without care."
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]
## Sketch
[Notes or a checklist reflecting our understanding of the selected approach]
Contributor guide
Assessment
This issue has not been assessed yet.