Distillation

Date: Sep 10, 2026

• 🔴 (03:19) User’s compiled-bundle search found exactly 1 function getGitClient, 1 async function getGitClient, and 4 occurrences of getGitClient().
• 🔴 (03:19) getGitClient() at lines 57070–57079 uses getConfigFileDir() || ".", calls process.chdir(configFileDir), logs "Working directory:" with process.cwd(), creates the client via esm_default2(configFileDir), checks await git.checkIsRepo(), throws ConfigurationError("Not in a git repository!") if false, and otherwise returns createDryRunGit(git).
• 🔴 (03:19) Adjacent compiled helpers include stripRemoteName(branch, remoteName), which strips the ${remoteName}/ prefix when present, and createGitClient(directory), which returns createDryRunGit(esm_default2(directory)).
• 🔴 (03:19) The 3 call sites following the getGitClient() definition are: publishMain(argv) at line 241540, prepareMain(argv) at line 242166, and changelogMain(argv) at line 242554.
• 🔴 (03:19) publishMain(argv) obtains const git = await getGitClient() and either logs "Not checking the status of the local repository" when argv.noGitChecks is set or checks await git.status() and reports "Your repository is in a dirty state. Please stash or commit the pending changes." when isRepoDirty(repoStatus) is true.
• 🔴 (03:19) prepareMain(argv) obtains let git = await getGitClient(); when argv.configFrom is set, it warns that remote .craft.yml and its preReleaseCommand must be trusted, fetches [argv.remote, argv.configFrom], reads ${argv.remote}/${argv.configFrom}:${CONFIG_FILE_NAME}, and passes the content to loadConfigurationFromString(configContent).
• 🔴 (03:19) changelogMain(argv) obtains const git = await getGitClient(); absent argv.since, it attempts to derive tagPrefix via findConfigFile() and getGitTagPrefix(), logs "Could not read tag prefix from config; using latest tag overall" on failure, and calls getLatestTag(git, tagPrefix).
• 🔴 (03:19) User’s compiled-bundle search found exactly 0 setRemoteUrl occurrences, 0 "remote set-url" occurrences, and 5 addRemote occurrences.
• 🔴 (03:19) The located addRemote code belongs to bundled Git task/client plumbing: addRemoteTask(remoteName, remoteRepo, customArgs) builds ["remote", "add", ...customArgs, remoteName, remoteRepo]; remote_exports exports addRemoteTask; and Git2.prototype.addRemote(remoteName, remoteRepo, then) invokes addRemoteTask2(remoteName, remoteRepo, getTrailingOptions2(arguments)) through _runTask.