-
Notifications
You must be signed in to change notification settings - Fork 6
Enhance our Pepr Debugging docs #1776
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
Comments
@samayer12 This ticket came out of retro, do you think there needs to be more docs on top of the ones that exist now? https://docs.pepr.dev/main/best-practices/#debugging Is there anything specific that you would want to see? |
This was referenced Feb 10, 2025
Merged
github-merge-queue bot
pushed a commit
that referenced
this issue
Feb 10, 2025
## Description This PR makes minor changes to debugging docs and applies some IDE-suggested `.md` fixes. End to End Test: <!-- if applicable --> (See [Pepr Excellent Examples](https://github.com/defenseunicorns/pepr-excellent-examples)) ## Related Issue Fixes #1776 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [x] Other (security config, docs update, etc) ## Checklist before merging - [x] Unit, [Journey](https://github.com/defenseunicorns/pepr/tree/main/journey), [E2E Tests](https://github.com/defenseunicorns/pepr-excellent-examples), [docs](https://github.com/defenseunicorns/pepr/tree/main/docs), [adr](https://github.com/defenseunicorns/pepr/tree/main/adr) added or updated as needed - [x] [Contributor Guide Steps](https://docs.pepr.dev/main/contribute/#submitting-a-pull-request) followed
github-merge-queue bot
pushed a commit
that referenced
this issue
May 29, 2025
## Description While working on #1776, I noticed that we do not use a markdown linter. We should lint our markdown code since it's used to create user-facing documentation. This PR adds `markdownlint-cli` as a project dependency and configures `.md` linting upon commit. ## Related Issue Fixes #2120 Relates to #1776 ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [x] Other (security config, docs update, etc) ## Checklist before merging - [x] Unit, [Journey](https://github.com/defenseunicorns/pepr/tree/main/journey), [E2E Tests](https://github.com/defenseunicorns/pepr-excellent-examples), [docs](https://github.com/defenseunicorns/pepr/tree/main/docs), [adr](https://github.com/defenseunicorns/pepr/tree/main/adr) added or updated as needed - [x] [Contributor Guide Steps](https://docs.pepr.dev/main/contribute/#submitting-a-pull-request) followed --------- Signed-off-by: Case Wylie <[email protected]> Co-authored-by: Case Wylie <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Describe what should be investigated or refactored
https://docs.pepr.dev/main/best-practices/#debugging Needs to include how to tell if a watch event was caught, and if a resource was mutated.
The text was updated successfully, but these errors were encountered: