You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe what should be investigated or refactored
With the root level markdown files now being pulled directly into the Pepr docs website, we need to review/update the markdown files in the Pepr Core docs folder to remove duplicate content, update links, and revise as needed for consistent style.
…#804)
## Description
With the root level markdown files now being pulled directly into the
Pepr docs website, we need to review/update the markdown files in the
Pepr Core docs folder to remove duplicate content, update links, and
revise as needed for consistent style.
...
## Related Issue
Fixes#802
<!-- or -->
Relates to #
## Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Other (security config, docs update, etc)
## Checklist before merging
- [ ] Test, docs, adr added or updated as needed
- [ ] [Contributor Guide
Steps](https://docs.pepr.dev/main/contribute/contributor-guide/#submitting-a-pull-request)
followed
Describe what should be investigated or refactored
With the root level markdown files now being pulled directly into the Pepr docs website, we need to review/update the markdown files in the Pepr Core docs folder to remove duplicate content, update links, and revise as needed for consistent style.
Links to any relevant code
(optional) i.e. -
pepr/README.md
Line 3 in 24f1f25
Additional context
Add any other context or screenshots about the technical debt here.
The text was updated successfully, but these errors were encountered: