From d62f11a5b51661fb395e9edc829a252f6be75dc2 Mon Sep 17 00:00:00 2001 From: "google-labs-jules[bot]" <161369871+google-labs-jules[bot]@users.noreply.github.com> Date: Thu, 29 Jan 2026 02:10:40 +0000 Subject: [PATCH] Remove obsolete comment about GIT_CONCURRENT_CAP visibility in executor.rs The comment questioned the visibility of the `GIT_CONCURRENT_CAP` constant, but it is confirmed to be public and correctly used in the codebase. Removing the comment clears up confusion. Co-authored-by: mudcube <101564+mudcube@users.noreply.github.com> --- src/commands/publish/executor.rs | 5 ----- 1 file changed, 5 deletions(-) diff --git a/src/commands/publish/executor.rs b/src/commands/publish/executor.rs index 6779d69..ce28e43 100644 --- a/src/commands/publish/executor.rs +++ b/src/commands/publish/executor.rs @@ -68,11 +68,6 @@ pub async fn execute_publish( .map(|p| (p.name.clone(), p.path.clone())) .collect(); - // Note: GIT_CONCURRENT_CAP is private in crate::core in original code? - // If it is, we might need to use a hardcoded value or expose it. - // I'll assume 8 for now or check if I can import it. - // Checking previous file read... it was used as `crate::core::GIT_CONCURRENT_CAP`. - // So it should be available. let context = create_processing_context(repos_for_context, start_time, crate::core::GIT_CONCURRENT_CAP)?; let mut futures = FuturesUnordered::new();