Skip to content

make repo-memory available before scheduling #22

@mrjf

Description

@mrjf

github/gh-aw#24345 (comment)

The repo-memory clone step occurs after Check which programs are due, so the scheduling script cannot see persisted state from previous runs. This causes incorrect selection/skip behavior. Reorder so repo-memory is available before the scheduling step, or move scheduling into the agent phase after repo-memory is cloned.

This issue also appears on line 445 of the same file.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions