GH-572: Document Config Server behavior when Git backend is unavailable#3251
Open
won-seoop wants to merge 1 commit into
Open
GH-572: Document Config Server behavior when Git backend is unavailable#3251won-seoop wants to merge 1 commit into
won-seoop wants to merge 1 commit into
Conversation
…is unavailable Add a new section "Behavior When the Git Backend is Unavailable" with four sub-sections explaining the different failure scenarios: - Startup: lazy-clone vs clone-on-start fail-fast behavior - Runtime: local working copy fallback when remote is down - Local copy drift: how force-pull prevents stale local state - Client refresh: what happens when a refresh is triggered while the backend is unreachable Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Summary
Adds a new "Behavior When the Git Backend is Unavailable" section to
git-backend.adoccovering the four scenarios requested in the original issue:clone-on-start: true(fail-fast), and points to the health indicator for post-startup detection.force-pullsection.Related issue
Closes #572
🤖 Generated with Claude Code