Repository navigation
docs: add README FAQ answering common search queries (#43) - #46
Open
mafujahmedridoy22-commits wants to merge 1 commit into
Open
mafujahmedridoy22-commits wants to merge 1 commit into
mafujahmedridoy22-commits wants to merge 1 commit into
Conversation
Short, search-shaped Q&A pairs covering the validate-vs-apply gap, the refusals, AWS-only, zero dependencies, and stub stacks — each honest about current limits and linked to the tracking issues. Closes ehtishammubarik#43
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
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.
Fixes #43
Adds a README FAQ section with seven search-phrased Q&A pairs covering: why
validate isn't enough, what stackmason refuses and why, why it is AWS-only,
what "zero dependencies" means in practice, what happens when a stub stack is
picked, and the current CI plan-gate gap. Each answer is honest about current
limits and links the relevant tracking issues (#3, #10, #12, #31).