Repository navigation
Correct Git recovery guidance and verify repository outcomes - #1
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.
Git output previously selected unsafe or unsupported recovery steps: GH013 alone implied a secret, protected-branch fixes hard-reset dirty work, and generic conflict or unknown output received confident advice. Shared recipes now require explicit evidence and stated prerequisites, preserve dirty work when publishing a review branch, distinguish merge from rebase, and limit secret cleanup to verified latest unpublished commits.
The existing content is organized into Fix a problem, Learn Git, and Find a command, with retained deep links, search/history restoration, and corrected teaching claims.
Validation: 193 parser/data/source assertions and 29 executable disposable-repository scenarios passed locally, including PowerShell and Git Bash command execution. Desktop/mobile Chromium journeys passed against the minified artifact, with shared-data equality, copy, keyboard, focus, reduced-motion, sampled contrast, and overflow checks. This PR adds Ubuntu CI checks; Pages runs the recovery tests before deployment.
Provider policy engines, real credential rotation/login, arbitrary history cleanup, other browsers, and a full accessibility audit remain outside local verification. Baseline inventory, task tracker, and release evidence are under docs/recovery-audit/ and docs/recovery-task-tracker.md. Production verification follows deployment, as authorized by the user.