feat(v1.2.0): add start-here callout and refine risk guidance#2
Open
ikelaiah wants to merge 2 commits into
Open
feat(v1.2.0): add start-here callout and refine risk guidance#2ikelaiah wants to merge 2 commits into
ikelaiah wants to merge 2 commits into
Conversation
- Add dismissible "Start here" callout on both pages, persisted in localStorage; overview links to the Beginner Daily Path, branch map points at the create-from-commit flow. - Soften `git reset --soft HEAD~1` from danger to caution since it keeps edits staged; expand the note to warn against using it on shared commits. - Pair the diverged-scenario `git merge origin/<branch>` suggestion with a preceding `git fetch` so the two-step recovery is explicit; update the summary to match. - Move shared callout setup into src/version.js so both HTML pages reuse the same behaviour without duplicating code. - Bump version to 1.2.0 and update README and CHANGELOG.
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
index.htmlandbranch-map.html. Overview links to the Beginner Daily Path; branch map points at the create-from-commit flow. Dismissed state is stored inlocalStorageundergit-map-start-here-dismissed.git reset --soft HEAD~1fromdangertocaution. A soft reset keeps your edits staged, so the previous danger framing was stronger than warranted. The note now also reminds users to avoid it on commits they have already shared.git merge origin/<branch>recommendation in the diverged scenario with agit fetch+git merge origin/<branch>pair, and update the summary so the two-step path reads naturally next to rebase and merge.Why
This release came out of a project review focused on first-load orientation and command accuracy. Beginners landing on the overview see a wide map and three control groups without a clear "start here" signpost, and the diverged scenario was suggesting a merge against a remote-tracking branch without the fetch that makes it work. The soft-reset risk tier was also miscalibrated against the existing
cautiontier used for similar reversible operations.Changes
src/data.js—reset-softrisk and note; diverged scenarionextandsummary.index.html,branch-map.html— newstart-hereaside;#daily-pathanchor on the overview.src/styles.css—.start-herecomponent styles.src/version.js— bumped to1.2.0; added sharedsetupStartHerewithlocalStoragepersistence so both pages reuse the same behaviour.README.md,CHANGELOG.md— version badge, 1.2 intro paragraph, full 1.2.0 entry.Test plan
node scripts/validate.mjspasses.index.htmlin a fresh browser profile — callout appears under the intro, the link scrolls to the Beginner Daily Path, dismiss button hides it, and reload keeps it hidden.branch-map.htmlin the same profile — callout stays dismissed across both pages because they share the storage key.localStorageand verify the callout reappears on next load.reset --softcard now shows thecautionbadge instead ofdanger, and the spotlight note mentions keeping edits staged.git pull --rebase,git pull --no-rebase,git fetch,git merge origin/<branch>in that order, and the summary mentions the fetch-then-merge option.v1.2.0label renders in the header of both pages.