Fix getRepoSnapshot tree SHA fallback and remove unconditional branch lookup

[Copilot]

This addresses all unresolved comments in the linked review thread for PR #166. The reported issues were an invalid tree_sha fallback (using commit SHA) and an extra getBranch call on the success path.

• Tree fetch flow simplified

  • git.getTree now first uses repoInfo.default_branch directly.
  • repos.getBranch is no longer called on every successful repository snapshot request.

• Fallback now resolves a real tree SHA

  • On initial tree fetch failure, fallback resolves branch.commit.commit.tree.sha.
  • If missing, fallback fetches the commit object via git.getCommit(commit_sha) and uses commit.tree.sha (instead of passing commit SHA to getTree).

• Failure semantics preserved

  • If fallback resolution cannot produce a tree SHA, the original tree-fetch error is rethrown.

try {
  ({ data: repoTree } = await client.rest.git.getTree({
    owner,
    repo,
    tree_sha: repoInfo.default_branch,
  }));
} catch (initialTreeError) {
  const { data: branch } = await client.rest.repos.getBranch({ owner, repo, branch: repoInfo.default_branch });
  let resolvedTreeSha = getNestedString(branch, ["commit", "commit", "tree", "sha"]);

  if (!resolvedTreeSha) {
    const commitSha = getNestedString(branch, ["commit", "sha"]);
    if (commitSha) {
      const { data: commit } = await client.rest.git.getCommit({ owner, repo, commit_sha: commitSha });
      resolvedTreeSha = commit.tree?.sha;
    }
  }

  if (!resolvedTreeSha) throw initialTreeError;

  ({ data: repoTree } = await client.rest.git.getTree({ owner, repo, tree_sha: resolvedTreeSha }));
}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
readme-gen-ai	Ready	Preview, Comment	May 31, 2026 7:33am

[naheel0]

@copilot resolve the merge conflicts in this pull request