On Fri, Oct 25, 2013 at 03:33:46PM +0100, Pedro Alvarez wrote:
---
yarns/branches-workspaces.yarn | 12 ++++++------
yarns/implementations.yarn | 23 ++++++++++++++++++++++-
yarns/regression.yarn | 14 ++++++++++++++
3 files changed, 42 insertions(+), 7 deletions(-)
create mode 100644 yarns/regression.yarn
diff --git a/yarns/branches-workspaces.yarn b/yarns/branches-workspaces.yarn
index cd3f7a0..c015a8f 100644
--- a/yarns/branches-workspaces.yarn
+++ b/yarns/branches-workspaces.yarn
@@ -47,7 +47,7 @@ Once we have a workspace, we can check out a system branch.
SCENARIO check out an existing system branch
GIVEN a workspace
AND a git server
- WHEN checking out the master system branch
+ WHEN checking out the master system branch/tag
This doesn't make for good English. I would prefer it allowing either
branch or tag, rather than needing to specify that it may be either.
More importantly, it's sort-of still a system branch even if it's from
a tag.
<snip a bunch of IMPLEMENTS WHEN renames>
- IMPLEMENTS WHEN checking out the (\S+) system branch
+ IMPLEMENTS WHEN checking out the (\S+) system branch/tag
IMPLEMENTS WHEN checking out the (\S+) system (branch|tag)
cd "$DATADIR/workspace"
run_morph checkout test:morphs "$MATCH_1"
@@ -496,3 +510,10 @@ variables in `$DATADIR/env`. We treat the value as a format string
for
IMPLEMENTS GIVEN an environment variable (\S+) containing "(.*)"
printf "export $MATCH_1=$MATCH_2" >> "$DATADIR/env"
+
+Implementations for building systems
+------------------------------------
+
+ IMPLEMENTS THEN morph build the system (\S+) of the branch/tag (\S+) of the repo
(\S+)
s/branch\/tag/(branch|tag)/