Skip to content

docs(faq): say where an update lands when the agent runs in a git worktree - #160

Open
vliggio wants to merge 1 commit into
career-ops-hq:mainfrom
vliggio:claude/career-ops-doc-changes-ea2117
Open

vliggio wants to merge 1 commit into
career-ops-hq:mainfrom
vliggio:claude/career-ops-doc-changes-ea2117

Conversation

@vliggio

@vliggio vliggio commented Oct 10, 2026

Copy link
Copy Markdown
Contributor

What

One new FAQ entry, placed after "Where does my data live?":

My agent runs in a git worktree. Where does a career-ops update land?

It says the update lands on main in the checkout that has main checked out, gives the git merge main step for the worktree you are in, names the two cases where apply and rollback refuse (no checkout has main; the main checkout has uncommitted changes to tracked files), and gives the CAREER_OPS_UPDATE_IN_WORKTREE=1 opt-out.

Why

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. 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) and docs/SCRIPTS.md on core main.

Hold until the next core release

Same reason as #145: the latest release is still v1.35.0, and its update-system.mjs does not have the redirect (checked at the career-ops-v1.35.0 tag). 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 entry
  • content/docs/faq.{es,fr,de}.mdx: the same entry, restamped with node .i18n/hash.mjs (all three were current with the English before this change)
  • src/lib/faq-data.ts: regenerated with node scripts/faq-from-mdx.mjs

Conflict with #145

Both PRs restamp translationHash in faq.{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 --selftest and scripts/verify-agent-layer.mjs against the local build all pass.

🤖 Generated with Claude Code

…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
vliggio requested a review from santifer as a code owner October 10, 2026 01:13
@vercel

vercel Bot commented Oct 10, 2026

Copy link
Copy Markdown

@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.

@coderabbitai

coderabbitai Bot commented Oct 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You'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.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Configuration used: Repository: career-ops-hq/career-ops-docs/.coderabbit.yaml
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: dcfd8c13-2b0b-4a1f-8388-99eccf53d787

📥 Commits

Reviewing files that changed from the base of the PR and between f217ca5 and 007ac83.


📒 Files selected for processing (5)
  • content/docs/faq.de.mdx
  • content/docs/faq.es.mdx
  • content/docs/faq.fr.mdx
  • content/docs/faq.mdx
  • src/lib/faq-data.ts


  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant