Ignore Forge metadata in Git state checks - #282
Open
eshulman2 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.forgedirectory when detecting user-facing workspace changesWhy
The task agent commits implementation changes inside the container while leaving
.forge/untracked. The host then saw.forge/ingit status, excluded it during staging, and attempted an empty commit. That failed the otherwise successful task and caused an unnecessary retry.Validation
uv run ruff format src/forge/workspace/git_ops.py tests/unit/workspace/test_git_ops_commit.pyuv run ruff check src/forge/workspace/git_ops.py tests/unit/workspace/test_git_ops_commit.pyuv run pytest tests/unit/workspace/test_git_ops_commit.py tests/unit/workspace/test_git_ops_redaction.py -q(6 passed)