From 4d794d475e01363928916f7667a63eed6071f5e2 Mon Sep 17 00:00:00 2001 From: Richard Maw Date: Sun, 10 Aug 2014 20:29:41 +0100 Subject: yarns: Start from petrified refs This is closer to our current workflow, where we are always petrified and update the ref field when we need to update a component. This required rearranging the operations to create the chunk repository before the definitions repository, and remove a check that assumes we weren't already petrified. --- yarns/branches-workspaces.yarn | 1 - 1 file changed, 1 deletion(-) (limited to 'yarns/branches-workspaces.yarn') diff --git a/yarns/branches-workspaces.yarn b/yarns/branches-workspaces.yarn index 995a9450..2f617ce4 100644 --- a/yarns/branches-workspaces.yarn +++ b/yarns/branches-workspaces.yarn @@ -178,7 +178,6 @@ all the refs are unchanged. GIVEN a workspace AND a git server WHEN the user creates a system branch called foo - THEN in branch foo, stratum strata/test-stratum.morph refs test-chunk in master Edit the chunk. We make use of special knowledge here: `test:test-chunk` is a chunk repository created in the mocked git server, for testing -- cgit v1.2.1