summaryrefslogtreecommitdiff
path: root/tests.branching/morph-tag-fails-if-tag-exists.script
Commit message (Collapse)AuthorAgeFilesLines
* Rename morph tag tests to follow patternSam Thursfield2013-01-221-33/+0
| | | | The pattern is COMMAND-assertion, not morph-COMMAND-assertion.
* Fix bashism in morph tag test scriptsJannis Pohlmann2012-12-131-1/+1
|
* Add an initial implementation of "morph tag"Jannis Pohlmann2012-12-131-0/+33
In order to make releases and freeze system branches entirely, we need to be able to 100% petrify a system branch (that is, resolve ALL refs into SHA1s) and tag this state to be able to check it out again later. This is essentially what "morph tag" does. It takes a tag name and an arbitrary amount of arguments to "git tag", petrifies all morphologies of the current system branch behind the scenes, creates a dangling commit and attaches an annotated tag to it. Petrifying in this case means that all refs used for chunks are resolved into commit SHA1s. For stratum and system morphologies, the refs are replaced by the name of the tag that's being created. The "tag" command also supports tagging when stratum morphologies are spread across multiple repositories. In this case, it will include all statum morphologies from other repos in the tag commi in the branch root repo. The references to these morphologies are updated so that they point to the branch root repo and the tag being created. This commit also adds a few tests for "morph tag" to verify that all this works.