extract debug info #64
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rfay
approved these changes
Oct 18, 2024
stasadev
force-pushed
the
20241018-extract-debug
branch
from
a60721b
to
f41cacc
Compare
stasadev
approved these changes
Oct 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Issue
I've started dropping this section from addons I create because adds noise to the main readme.
How This PR Solves The Issue
Extracts information to a seperate file,
README_DEBUG.mdUpdates TOC link to
README_DEBUG.md.The idea here is we still want to keep the debug information present and available, but not overwhelm addon user with addon developer technical details.
Manual Testing Instructions
Automated Testing Overview
Related Issue Link(s)
Release/Deployment Notes