crates/gitbutler-branch-actions/src/status.rs

@@ -1,6 +1,5 @@
 use std::{collections::HashMap, path::PathBuf, vec};
 
-use crate::integration::get_workspace_head;
 use crate::{
     conflicts::RepoConflictsExt,
     file::{virtual_hunks_into_virtual_files, VirtualBranchFile},
@@ -17,6 +16,7 @@ use gitbutler_command_context::CommandContext;
 use gitbutler_diff::{diff_files_into_hunks, GitHunk, Hunk, HunkHash};
 use gitbutler_operating_modes::assure_open_workspace_mode;
 use gitbutler_project::access::WorktreeWritePermission;
+use gitbutler_repo::RepositoryExt;
 use tracing::instrument;
 
 /// Represents the uncommitted status of the applied virtual branches in the workspace.
@@ -51,7 +51,7 @@ pub fn get_applied_status_cached(
     //           calculate which should already be 'fixed' - why do we have the integration branch
     //           if we can't assume it's in the right state? So ideally, we assure that the code
     //           that affects the integration branch also updates it?
-    let integration_commit_id = get_workspace_head(ctx)?;
+    let integration_commit_id = ctx.repository().head_commit()?.id();
     let mut virtual_branches = ctx
         .project()
         .virtual_branches()