We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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:
@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?
Sorry, something went wrong.
chore: tidy up docs (#1802)
de10031
## 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
samayer12
Successfully merging a pull request may close this issue.
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: