Skip to content

Commit cce3387

Browse files
committed
docs(ci): say why the overlay's ancestry tie goes to main
The comment claimed a line fresh off main is the same as main, but the cozystack-packages:main artifact is built from main's tip, not from the cut commit. Once main moves past the cut, a stack on such a line gets newer images than the line's, until the stack holds a commit of the line's own. State that limit, and why the tie still goes to main: a branch forked from main before a cut ties the same way and is far more common. Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <[email protected]>
1 parent 9c5c5f9 commit cce3387

1 file changed

Lines changed: 7 additions & 3 deletions

File tree

‎.github/workflows/pull-requests.yaml‎

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -642,9 +642,13 @@ jobs:
642642
# A base that is neither main nor a line (a stacked PR's feature branch) has
643643
# no artifact, and a `/` in it is not even a valid OCI tag. It reads the
644644
# artifact of whichever of main and the lines it has the fewest commits on
645-
# top of. A tie goes to main, so a stack on a line keeps that line's
646-
# generation only once the line has a commit of its own: a line fresh off
647-
# main is topologically the same as main at that commit.
645+
# top of. A tie goes to main. A line with no commit of its own yet is, in
646+
# the graph, main at the cut commit, so a stack on it ties and reads the
647+
# artifact built from main's tip. That artifact carries newer images than
648+
# the line once main moves past the cut. The stack keeps reading it until
649+
# it contains a commit of the line's own. Breaking the tie towards the
650+
# line instead would misroute the far more common branch forked from main
651+
# before the cut, which ties the same way.
648652
#
649653
# A missing artifact stays a no-op (packages keep their committed refs), which
650654
# also covers a line whose first build-release run has not landed yet.

0 commit comments

Comments
 (0)