docs: add configuration documentation - #806
Open
spike-rabbit wants to merge 1 commit into
Open
Conversation
spike-rabbit
force-pushed
the
docs/configuration-documentation
branch
from
August 17, 2026 10:17
e1e5f60 to
828bf40
Compare
fh1ch
requested changes
Aug 18, 2026
fh1ch
left a comment
fh1ch
left a comment
Member
There was a problem hiding this comment.
@spike-rabbit tiny nit and one simple question, the rest is flawless. Let me know what you think 🏓
spike-rabbit
force-pushed
the
docs/configuration-documentation
branch
from
August 21, 2026 07:42
828bf40 to
21e76f6
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
Configuration documentation is not available.
What is the new behavior?
Added configuration documentation.
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:
See #805