Repository navigation
fix: stop scode-build-goal goal files from naming the checkout path - #528
Merged
Merged
Conversation
scode-build-goal writes goal files that a later session runs unattended with /goal. It told the planning session to write every path in a goal file in absolute form, the repository root included. A goal planned in one clone of a project therefore named that clone in its header, pointed its disk and memory watchdog at that clone, and recorded the commit that clone's main branch was at. Run from a second clone of the same project, the goal file described a checkout the session was not in, and the watchdog watched the wrong directory. Goal files now assume they are started inside a checkout of the project, name the project by its GitHub remote rather than by a path, and leave the checkout's current state for the run to read. Paths outside the checkout, such as the working log and the watchdog's files, stay absolute. Before writing anything, the executing session now checks that its working directory is in a checkout of that project, and stops and tells the user when it is not. Writing the log from the wrong directory would make the next run, started from the right one, resume from it.
scode
force-pushed
the
scode-build-goal-no-checkout-path
branch
from
November 16, 2026 02:01
ff7c280 to
2908b3b
Compare
scode
marked this pull request as ready for review
November 16, 2026 02:01
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
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.
scode-build-goal writes goal files that a later session runs unattended with
/goal. It told the planning session to write every path in a goal file in
absolute form, the repository root included. A goal planned in one clone of a
project therefore named that clone in its header, pointed its disk and memory
watchdog at that clone, and recorded the commit that clone's main branch was
at. Run from a second clone of the same project, the goal file described a
checkout the session was not in, and the watchdog watched the wrong directory.
Goal files now assume they are started inside a checkout of the project, name
the project by its GitHub remote rather than by a path, and leave the
checkout's current state for the run to read. Paths outside the checkout, such
as the working log and the watchdog's files, stay absolute.
Before writing anything, the executing session now checks that its working
directory is in a checkout of that project, and stops and tells the user when
it is not. Writing the log from the wrong directory would make the next run,
started from the right one, resume from it.