Uh oh!
There was an error while loading. Please reload this page.
Clone repo-memory branch before scheduling pre-step - #23
Merged
Conversation
The repo-memory clone step (from the tools: section) was placed after the "Check which programs are due" pre-step by the gh-aw compiler, so the scheduling script could not read persisted state from previous runs. This caused incorrect selection/skip behavior. Fix: add an explicit shallow clone of the memory/autoloop branch as a new pre-step that runs before the scheduling step, ensuring state files are available when scheduling decisions are made. Also adds tests to verify the step ordering invariant. Agent-Logs-Url: https://github.com/githubnext/autoloop/sessions/3013e45a-953d-4f06-bdab-ed720379b412 Co-authored-by: mrjf <180956+mrjf@users.noreply.github.com>
…tests Agent-Logs-Url: https://github.com/githubnext/autoloop/sessions/3013e45a-953d-4f06-bdab-ed720379b412 Co-authored-by: mrjf <180956+mrjf@users.noreply.github.com>
CopilotAI
changed the title
[WIP] Fix repo-memory availability before scheduling stepClone repo-memory branch before scheduling pre-stepApr 4, 2026
mrjf
marked this pull request as ready for review
April 4, 2026 04:52
Uh oh!
There was an error while loading. Please reload this page.
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The gh-aw compiler places the framework-managed repo-memory clone step after all user-defined pre-steps. This means the "Check which programs are due" scheduling script reads from an empty
/tmp/gh-aw/repo-memory/autoloopdirectory, treating every program as a first run and producing incorrect selection/skip decisions.Changes
workflows/autoloop.md: Added a newClone repo-memory for schedulingpre-step before the scheduling step that performs an early shallow clone of thememory/autoloopbranch. Gracefully handles first-run (no branch yet) by creating an empty directory.tests/test_scheduling.py: AddedTestWorkflowStepOrderingto assert the clone step exists and precedes the scheduling step, preventing future regressions.Compiled workflow step order (before → after)