[Bug] Large diffs cause commit/push/PR action to fail.

[jcampuza]

Probably an edge case, but large changes currently cause the git commit/push action to fail. Of course its encouraged to make smaller changes, but I went ahead and had codex do a full migration from pnpm to bun and a monorepo for one of my apps and it causes this action to fail.

Screenshot attached:

This appears to occur because the git diff/patch is needed to generate a summary of the changes for the PR description/body that is created with this action. Maybe a graceful fallback could be introduced that if the limit is exceeded return a truncated flag, and fallback the description that is generated to something indicating a large diff was detected.

In apps/server/src/git/Layers/GitService.ts

if (bytes > maxOutputBytes) {
        return yield* new GitCommandError({
          operation: input.operation,
          command: quoteGitCommand(input.args),
          cwd: input.cwd,
          detail: `${quoteGitCommand(input.args)} output exceeded ${maxOutputBytes} bytes and was truncated.`,
        });
      }

Sidenote: The error text appears to indicate it was "truncated" but in reality its just an error, since in reality the operation was simply aborted.

How to reproduce

Generate a very large diff on a repo and then try to use the git commit and push/pr action button.

Suggestion

Suggestions could any of the following:

• Gracefully fallback if the limit was exceeded to a fallback PR body/description - generate a generic PR description that just says the diff was very large and to review manually or that automated summary was not able to be generated.
• Alternatively just use what was able to be gathered to generate the summayr but append that the automated summary used limited context.

Other mild suggestions

• Common reasons this might occur would be lockfile changes or large generated files, maybe if common lockfiles are detected they are pruned from the summary collection?

[eliesgalvira]

I ran into the same issue when trying to commit from a git worktree a 9590552 byte diff (~9.6MB). The action failed while building the staged patch, the error was (GPT-5.4 transcribed it since I couldn't copy to clipboard the error message):

Action failed
Error: Git command failed in GitCore.prepareCommitContext.stagedPatch:
git diff --cached --patch --minimal (/home/redacted/.t3/worktrees/redacted/t3code-cc34f1fc) - git diff --cached --patch --minimal output exceeded 1000000 bytes and was truncated. at Array. (file:///tmp/bunx-1000-t3@alpha/node_modules/t3/dist/index.mjs:3330:45) at Effect.fn (file:///tmp/bunx-1000-t3@alpha/node_modules/t3/dist/index.mjs:3356:5) at Effect.fn (definition) (file:///tmp/bunx-1000-t3@alpha/node_modules/t3/dist/index.mjs:3324:30) at Effect.fn (file:///tmp/bunx-1000-t3@alpha/node_modules/t3/dist/index.mjs:16327:9) at Effect.fn (definition) (file:///tmp/bunx-1000-t3@alpha/node_modules/t3/dist/index.mjs:15842:29)

[akshaylingamaneni]

ran in to the same issue, also was not able to close it or move it out. were you guys able to close it or it auto closed out? trying to understand if there is a ux bug as well

[akshaylingamaneni]

okay looks like, since t3code uses the underlying codex cli, it might be caused by codex cli being older and --ephemeral not present. I was on 0.77 and updated 0.98 dont see it again..

codex --version
codex-cli 0.114.0

[eliesgalvira]

ran in to the same issue, also was not able to close it or move it out. were you guys able to close it or it auto closed out? trying to understand if there is a ux bug as well

To close it I was able to drag the toast upwards, which made it disappear.

okay looks like, since t3code uses the underlying codex cli, it might be caused by codex cli being older and --ephemeral not present. I was on 0.77 and updated 0.98 dont see it again..

I updated codex as well and worked on pretty large diffs without issue, so this might be the fix.

Finally, I noticed there might be a duplicate of this issue at #567. So if this one's closed the other one probably should be as well.