Skip to content

Post-commit cache to avoid redundant work on consecutive commits #3

@jcleira

Description

@jcleira

Description

Introduce a lightweight post-commit cache (e.g., a small file in .partio/) that records which commit SHAs have already been fully processed. When the post-commit hook fires, check the cache first and skip processing if the commit was already handled. This prevents duplicate checkpoint writes when git operations trigger multiple hook invocations (e.g., rebases, merges, cherry-picks).

Source

Target Repos

  • cli

Acceptance Criteria

  • Post-commit hook records processed commit SHA in a cache file after successful processing
  • Hook is a no-op for commits already present in the cache
  • Cache file is stored in .partio/ and excluded from session metadata tracking
  • Cache does not grow unboundedly — prune entries older than N commits or days

Context Hints

  • cli/internal/hooks/
  • cli/internal/checkpoint/

Comment /minion build or add the minion-approved label to begin implementation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    minion-doneMinion execution completedminion-proposalFeature proposal from minion

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions