feat: add worktree feature with tests

[racgoo]

Summary

• Add 'worktree' feature with tests.

Changes

• Implement worktree-like methods in 'Repository'
• Add internal worktree features
• Add test code

Closes #172

[vercel]

@racgoo is attempting to deploy a commit to the Toss Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

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

Project	Deployment	Review	Updated (UTC)
es-git	Ready	Preview, Comment	Jan 2, 2026 7:21am

[seokju-na]

Can we make this method as function?

Other constructor methods (e.g. openRepository, initRepository also use functions instead of static methods, so it would be good to unify interfaces.

Also, is colud be better if it were async.

e.g.

#[napi]
/// @signature
/// ```ts
/// function openWorktreeFromRepository(
///   repo: Repository,
/// ): Promise<Worktree>;
/// ```
pub fn open_worktree_from_repository(...) -> AsyncTask<WorktreeOpenFromRepositoryTask> {
  todo!()
}

[racgoo]

@seokju-na Sorry for the late reply. spent some time thinking through the async design here.

My current thinking is to use AsyncTask only when the operation can be
expressed in terms of pure Rust values (e.g. String, PathBuf, primitive
types) that can safely be moved to a worker thread.

In cases like this one, a real AsyncTask is not possible because
napi-managed objects cannot be moved to worker threads.

One alternative is a fake-async Promise-based API (sync execution +
immediate resolve), which would require upgrading napi-rs to >= 3.7.1.

For reference, the implementation would look like this

pub fn open_worktree_from_repository(repo: &Repository, env: Env) -> crate::Result<PromiseRaw<'_,Worktree>> {
  let git2_worktree = git2::Worktree::open_from_repository(&repo.inner);
  match git2_worktree {
    Ok(worktree) => {
      Ok(PromiseRaw::resolve(&env, Worktree { inner: worktree })?)
    },
    Err(error) => {
      Ok(PromiseRaw::reject(&env, error.to_string())?)
    }
  }
}

Does this approach sound reasonable to you?