Repository navigation
Conversation
…ktree Core change career-ops-hq/career-ops#4738: from a linked git worktree, update-system.mjs re-runs check, apply, rollback and dismiss in the checkout that has main checked out, so the update is committed to main instead of the worktree's throwaway branch. New FAQ entry covering the redirect, the `git merge main` follow-up, the two cases where apply and rollback refuse, and the CAREER_OPS_UPDATE_IN_WORKTREE=1 opt-out. Same entry in the ES/FR/DE pages, restamped with .i18n/hash.mjs. src/lib/faq-data.ts regenerated with scripts/faq-from-mdx.mjs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@vliggio is attempting to deploy a commit to the Career Ops OSS Program Team on Vercel. A member of the Team first needs to authorize it. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 31 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (5)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This branch has not been deployed
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
One new FAQ entry, placed after "Where does my data live?":
It says the update lands on
mainin the checkout that hasmainchecked out, gives thegit merge mainstep for the worktree you are in, names the two cases whereapplyandrollbackrefuse (no checkout hasmain; themaincheckout has uncommitted changes to tracked files), and gives theCAREER_OPS_UPDATE_IN_WORKTREE=1opt-out.Why
Core change career-ops-hq/career-ops#4738: from a linked git worktree,
update-system.mjsre-runscheck,apply,rollbackanddismissin the checkout that hasmainchecked out. Someone whose agent session lives in a worktree runs the update, sees their branch unchanged, and has nowhere on the site to find out why.Companion to career-ops-hq/career-ops-docs#145, which adds the one-sentence note to the Windows page and the Windows FAQ entry. That PR deliberately keeps the full redirect behaviour off the Windows pages; this entry is where it goes. No overlap in the English text.
Verified against
update-system.mjs(worktreeUpdateTarget,redirectToMainCheckout) anddocs/SCRIPTS.mdon coremain.Hold until the next core release
Same reason as #145: the latest release is still v1.35.0, and its
update-system.mjsdoes not have the redirect (checked at thecareer-ops-v1.35.0tag). The entry says "ships in career-ops releases after v1.35.0", so it is accurate either way, but it only helps readers once that release is out.Changes
content/docs/faq.mdx: the new entrycontent/docs/faq.{es,fr,de}.mdx: the same entry, restamped withnode .i18n/hash.mjs(all three were current with the English before this change)src/lib/faq-data.ts: regenerated withnode scripts/faq-from-mdx.mjsConflict with #145
Both PRs restamp
translationHashinfaq.{es,fr,de}.mdx, so whichever merges second needs those three lines restamped. I will rebase this one once #145 lands.Checks
npm run types:check,npm run build,node scripts/faq-from-mdx.mjs --check,node scripts/verify-i18n-seo.mjs --selftestandscripts/verify-agent-layer.mjsagainst the local build all pass.🤖 Generated with Claude Code