Skip to content

fix: stop scode-build-goal goal files from naming the checkout path - #528

Merged
scode merged 1 commit into
mainfrom
scode-build-goal-no-checkout-path
Nov 16, 2026
Merged

scode merged 1 commit into
mainfrom
scode-build-goal-no-checkout-path

Conversation

@scode

@scode scode commented Nov 16, 2026

Copy link
Copy Markdown
Owner

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-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
scode force-pushed the scode-build-goal-no-checkout-path branch from ff7c280 to 2908b3b Compare November 16, 2026 02:01
@scode
scode marked this pull request as ready for review November 16, 2026 02:01
@scode
scode merged commit 67e360a into main Nov 16, 2026
5 checks passed
@scode
scode deleted the scode-build-goal-no-checkout-path branch November 16, 2026 02:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant