[pull] next from storybookjs:next#809
Merged
Merged
Conversation
Co-authored-by: Copilot <copilot@github.com>
Co-authored-by: Copilot <copilot@github.com>
…ookjs/storybook into feat/tanstack_automigrate
…stack-react.ts Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: Copilot <copilot@github.com>
…ookjs/storybook into feat/tanstack_automigrate
Co-authored-by: Copilot <copilot@github.com>
…ookjs/storybook into feat/tanstack_automigrate
…mits
`git status --porcelain` and `git diff` opportunistically refresh the
index stat-cache and write to `.git/index.lock` while doing so. The
change-detection scan invokes these commands frequently (every file
change is debounced into a scan; every git ref change re-runs
`isWorkingTreeClean()`), so the running dev server constantly grabs
`.git/index.lock`. When the user runs `git add`/`git commit` in their
shell, it races the dev server and fails with:
fatal: Unable to create '.git/index.lock': File exists.
Setting `GIT_OPTIONAL_LOCKS=0` on the execa env tells git to skip the
optional stat-cache refresh during read-only operations. Output of
`git status` / `git diff` remains correct; only the cache update is
skipped. This is the standard fix used by editors like VSCode for the
same reason.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: Copilot <copilot@github.com>
…locks Change-Detection: Set GIT_OPTIONAL_LOCKS=0 to avoid blocking commits
Tanstack: optimize react-store
CLI: Add react-vite to tanstack-react automigration
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )