Add a readme for the testexec extension and its conventions. #14
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
|
@TripleDogDare I'd love to request your review on this, since I think you've already become deeply familiar with it and will definitely spot any details that might be out of place :) |
|
Wow. Thanks. I took all of those and expanded in the areas that needed fixes too. This got much better as a result. |
Some typo fixes. Much more linking. A few more configuration hooks get mentions. Features have a pattern description before the literal example. Examples are more completely narrated. Added a whole section about script-vs-sequence (because the one tiny paranthetical about that wasn't even close to enough).
warpfork
force-pushed
the
testexec-docs
branch
from
9c5618d to
3c24d09
Compare
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.
This is a bit overdue :) Much of this was described in godocs or in comments in the code, but documentation deserves to be a little more discoverable than that!