v0 workspace repository identity and Git partial clone persistence issue

Help
1

I am working on a long-running project with GitHub integration.

Observed:

1. Workspace remote changed unexpectedly:

stageos-unified.git

↓

project.git

2. The workspace was using:

remote.origin.promisor=true

partialclonefilter=blob:none

3. After changing remote to the correct repository, Git push failed because missing promisor objects could not be fetched.

Impact:

- Cannot safely archive project history

- Cannot verify repository identity

- Long-running projects may lose deployment reliability

Request:

- Show whether workspace is full clone or partial clone

- Lock repository identity during a project session

- Warn before remote changes

- Prevent Git operations when workspace identity changes

2

While a member of our team prepares to jump in, you might find your answer even faster in our community resources.

3

Hi,

I’d be careful about treating the v0 workspace checkout as the source of truth once the remote identity has changed and promisor objects are missing.

With a partial clone, Git can leave some blobs out locally and fetch them later from the configured promisor remote. If the workspace was cloned from one repo and then origin was changed to another repo, Git may try to fetch missing objects from a remote that does not actually have those objects. That would explain why pushing/archive operations start failing even after correcting the remote URL.

For recovery, I’d use a fresh local clone of the intended GitHub repo instead of trying to repair the v0 workspace in place:

git clone --no-filter <correct-repo-url> stageos-unified-recovery
cd stageos-unified-recovery
git fsck --full

Then copy/export the latest app files from v0 into that clean clone, commit them on a new branch, and push that branch to GitHub. That gives you a clean repository identity and avoids pushing from a potentially inconsistent partial clone.

If you still have terminal access inside the v0 workspace, these checks would be useful to capture before changing anything else:

git remote -v
git config --get remote.origin.promisor
git config --get remote.origin.partialclonefilter
git branch -vv
git fsck --connectivity-only
git rev-list --objects --all --missing=print | head -50

I would avoid posting private repo URLs or tokens publicly, but the redacted output should make it clearer whether this is mainly a partial-clone recovery issue or a v0 Git workspace identity issue.