Skip to content

fix(scripts): new-worktree --compiler guard, yarn cleanup trap, and gitignore comment#36476

Open
iamdaven wants to merge 1 commit into
facebook:mainfrom
iamdaven:main
Open

fix(scripts): new-worktree --compiler guard, yarn cleanup trap, and gitignore comment#36476
iamdaven wants to merge 1 commit into
facebook:mainfrom
iamdaven:main

Conversation

@iamdaven
Copy link
Copy Markdown

--compiler without --claude now errors immediately. Previously the flag was silently ignored, which was confusing since it has no effect on its own.
yarn install failures now correctly trigger cleanup. Both installs were running in subshells ((cd ... && yarn)), which causes trap ERR to behave inconsistently across bash versions — the worktree could be left behind on a failed install. Replaced with direct cd && yarn in the current shell so the trap reliably fires.
Added a comment documenting valid .gitignore forms for .worktrees. The regex accepts /.worktrees, .worktrees/, and /.worktrees/ in addition to .worktrees, but nothing made that clear. A future contributor would likely "fix" it incorrectly without the comment.

…itignore check

- Error immediately if --compiler is passed without --claude instead of
  silently ignoring it
- Run yarn installs in the current shell instead of subshells so the ERR
  trap reliably fires and cleans up the worktree on failure
- Add comment documenting all valid .gitignore forms for .worktrees so
  the regex isn't incorrectly "fixed" by a future contributor
@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented May 14, 2026

Hi @iamdaven!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented May 14, 2026

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

@meta-cla meta-cla Bot added the CLA Signed label May 14, 2026
@meta-cla
Copy link
Copy Markdown

meta-cla Bot commented May 14, 2026

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant