Skip to content

The bug-fix agent does not know what the local cahnges are when following up on a Phabricator revision #6763

Description

@suhaibmujahid

Example https://phabricator.services.mozilla.com/D321460#11207132:

I diffed my tree against diff 1362809 hunk-by-hunk before pushing — it's identical

As now, when loading the revision, the revision diff gets applied to the tree but is uncommitted. We might need to have the diff committed when loading the revision or at least inform the agent that the changes are representing the target diff as part of the prompt, or both.

Though, having the diff committed might need accommodating that in the pipeline of collecting the changes and/or submitting an update.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Fields

    Priority

    None yet

    Effort

    Low

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions