Repository navigation
docs: add 'What is Exhibit?' section with concrete example (#1) - #7
Merged
Merged
Conversation
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.
What changed
Added a "What is Exhibit?" section to
README.mdright after the introduction paragraph, showing what goes in, what comes out, and execution time using a concrete example.Why
Fixes #1. Explains Exhibit's core value proposition in 30 seconds with a real example and expected output without requiring credentials or external API keys.
How it was verified
python3 -m unittest discover tests -v-> 44 tests, OKEvidence commit hashes
87d548dChecklist