Repository navigation
docs: recommend letting Shep install and set up bercail - #30
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.
The README's Quick start now leads with the easy path: get Shep, connect your computer, and ask it to set up bercail. In that first conversation Shep installs bercail (asking first), runs
bercail doctorandbercail bstack status, checks each repo, and connects the desk status webhooks.The mise / packslip / curl commands are unchanged, now under "Or install it yourself" (the release line and pin are still there for release bumps).
docs/install.mdpoints to Shep first.docs/shep.mdgets a "Let Shep set it up" section, and its intro now says bstack is the default stage.Checks: all
tests/*_test.shpass, and the relative links and anchors in the changed files resolve. README is 74 lines. Docs only.