git-multirepo 1.0.0.beta15 → 1.0.0.beta16

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 7e82b1d4dc7e0ce39b4b686b972ca4d71668129b
-  data.tar.gz: 0d7ea7821b543a7378d387105b694106683bcd45
+  metadata.gz: 46d5285daea9418ed3f43fc5e6b108bea2575915
+  data.tar.gz: 9a3952b8b0756e203b42e8363d7ffe7b65946c81
 SHA512:
-  metadata.gz: 8b96fd301dcf1160ce12f981a056f3a369972af9a1bf14741fc00bfed880f2ca2babbcc42a255bdfdb9416697b81cc069a5885fbbbf2870b8132ceae659c238a
-  data.tar.gz: e190376df8033efb5ebd67f302a0ea1243cbd30159c936969c25097db3406503411d5de24d90ffeac858791a5b16247103a45d45139942a2aedc479be2542064
+  metadata.gz: 7fc1808498483906126ba73d4ebd125f9f29c51e7465588bdbf15f7bff3774b564c7c9a7aca66202a9f8544aec11aea16fafc282c6c31b06acfd6f7c9941660b
+  data.tar.gz: 897ba9cb68e66d4631ae1ed41dae98ccb46c839392b0a5618ba5fe6820886b28d2f3e51a96c294d3ae512e414e5194837aec3a6c0136258f7686f1559b498e78

data/.gitignore

@@ -1,38 +1,38 @@
-*.gem
-*.rbc
-/.config
-/coverage/
-/InstalledFiles
-/pkg/
-/spec/reports/
-/test/tmp/
-/test/version_tmp/
-/tmp/
-
-## Specific to RubyMotion:
-.dat*
-.repl_history
-build/
-
-## Documentation cache and generated files:
-/.yardoc/
-/_yardoc/
-/doc/
-/rdoc/
-
-## Environment normalisation:
-/.bundle/
-/lib/bundler/man/
-
-# for a library or gem, you might want to ignore these files since the code is
-# intended to run in multiple environments; otherwise, check them in:
-# Gemfile.lock
-# .ruby-version
-# .ruby-gemset
-
-# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
-.rvmrc
-
-# Project-specific
-/.multirepo
-/.multirepo.lock
+*.gem
+*.rbc
+/.config
+/coverage/
+/InstalledFiles
+/pkg/
+/spec/reports/
+/test/tmp/
+/test/version_tmp/
+/tmp/
+
+## Specific to RubyMotion:
+.dat*
+.repl_history
+build/
+
+## Documentation cache and generated files:
+/.yardoc/
+/_yardoc/
+/doc/
+/rdoc/
+
+## Environment normalisation:
+/.bundle/
+/lib/bundler/man/
+
+# for a library or gem, you might want to ignore these files since the code is
+# intended to run in multiple environments; otherwise, check them in:
+# Gemfile.lock
+# .ruby-version
+# .ruby-gemset
+
+# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
+.rvmrc
+
+# Project-specific
+/.multirepo
+/.multirepo.lock

data/.rspec

@@ -1,2 +1,2 @@
---color
---require spec_helper
+--color
+--require spec_helper

data/Gemfile

@@ -1,4 +1,4 @@
-source 'https://rubygems.org'
-
-# Specify your gem's dependencies in git-multirepo.gemspec
-gemspec
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in git-multirepo.gemspec
+gemspec

data/Gemfile.lock

@@ -1,37 +1,37 @@
-PATH
-  remote: .
-  specs:
-    git-multirepo (0.0.1)
-      claide (~> 0.8, >= 0.8.0)
-      colored (~> 1.2)
-      os (~> 0.9.6)
-
-GEM
-  remote: https://rubygems.org/
-  specs:
-    claide (0.8.0)
-    colored (1.2)
-    diff-lcs (1.2.5)
-    os (0.9.6)
-    rake (10.4.2)
-    rspec (3.1.0)
-      rspec-core (~> 3.1.0)
-      rspec-expectations (~> 3.1.0)
-      rspec-mocks (~> 3.1.0)
-    rspec-core (3.1.7)
-      rspec-support (~> 3.1.0)
-    rspec-expectations (3.1.2)
-      diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.1.0)
-    rspec-mocks (3.1.3)
-      rspec-support (~> 3.1.0)
-    rspec-support (3.1.2)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  bundler (~> 1.7)
-  git-multirepo!
-  rake (~> 10.0)
-  rspec (~> 3.1.0)
+PATH
+  remote: .
+  specs:
+    git-multirepo (0.0.1)
+      claide (~> 0.8, >= 0.8.0)
+      colored (~> 1.2)
+      os (~> 0.9.6)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    claide (0.8.0)
+    colored (1.2)
+    diff-lcs (1.2.5)
+    os (0.9.6)
+    rake (10.4.2)
+    rspec (3.1.0)
+      rspec-core (~> 3.1.0)
+      rspec-expectations (~> 3.1.0)
+      rspec-mocks (~> 3.1.0)
+    rspec-core (3.1.7)
+      rspec-support (~> 3.1.0)
+    rspec-expectations (3.1.2)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.1.0)
+    rspec-mocks (3.1.3)
+      rspec-support (~> 3.1.0)
+    rspec-support (3.1.2)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.7)
+  git-multirepo!
+  rake (~> 10.0)
+  rspec (~> 3.1.0)

data/LICENSE

@@ -1,22 +1,22 @@
-The MIT License (MIT)
-
-Copyright (c) 2015 Michaël Fortin
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
-
+The MIT License (MIT)
+
+Copyright (c) 2015 Michaël Fortin
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+

data/README.md

@@ -1,137 +1,138 @@
-![git-multirepo](images/logo.png)
-
-# git-multirepo
-
-[![Gem Version](https://badge.fury.io/rb/git-multirepo.svg)](http://badge.fury.io/rb/git-multirepo)
-
-Track multiple Git repositories side-by-side.
-
-An alternative approach to manage constantly evolving dependencies.
-
-Check out [the project's to-do list](https://www.pivotaltracker.com/n/projects/1256156) to get an idea of upcoming enhancements.
-
-## Motivation
-
-By now the
-[pitfalls](http://somethingsinistral.net/blog/git-submodules-are-probably-not-the-answer/)
-of git submodules are
-[pretty](https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/)
-[well](http://slopjong.de/2013/06/04/git-why-submodules-are-evil/)
-[known](http://stackoverflow.com/questions/12075809/git-submodules-workflow-issues).
-They work when your dependencies are linearly-evolving third-party libraries that you seldom update but they fall apart when it comes to managing your own, constantly evolving dependencies.
-
-Git subtrees are the recommended alternative but have pitfalls of their own:
-
-- They require verbose and error-prone command-line operations. This can become quite tedious when managing more than one or two dependencies.
-- They change the rules of the game when it comes to merges.
-- Each developer has to configure the appropriate remotes and subtrees on his machine if he or she wants to contribute back.
-- Developers must not forget to push changes to dependencies back to the appropriate remotes.
-- Few git GUIs have any kind of subtree integration, so you're stuck with the command-line.
-
-Etc.
-
-## Overview
-
-Using git-multirepo, you can manage your main project and its dependencies as completely independent repositories while still maintaining the ability to checkout a previous revision in a single step and have the project build properly.
-
-A git-multirepo setup looks like this:
-
-```
-MyAwesomeProject
-  |-- AwesomeApp
-  |-- Dependency1
-  |-- Dependency2
-```
-
-In essence:
-
-1. You tell git-multirepo what your dependencies are.
-2. Each time you commit the main repo, git-multirepo tracks what revision of each dependency is required by the project (don't worry, it ensures that you don't forget to commit changes to dependencies beforehand; more on that later).
-3. If you ever want to go back to a previous version of your project, git-multirepo handles checking out the main repo and appropriate revisions of all of its dependencies in a single, seamless operation.
-4. Setting up the project on a new machine is only a single `git clone` and `multi install` away.
-
-## Example
-
-Say you want to track an existing project with git-multirepo:
-
-1. Organize repos on disk in the following manner:
-
-	```
-	MyAwesomeProject
-	  |-- AwesomeApp
-	  |-- Dependency1
-	  |-- Dependency2
-	```
-
-2. `cd` into the *AwesomeApp* directory (aka the "main repo").
-3. Run `multi init`.
-4. You will get prompted to add *Dependency1* and *Dependency2* to multirepo; do so.
-5. git-multirepo reads all required information from dependency repos and initializes itself, storing its metadata files in the main repo, under version control.
-
-From now on, each time you commit the main repo git-multirepo tracks — using a pre-commit hook — which revision of each dependency is required for that main repo revision, and where to get them. The pre-commit hook also ensures that you won't commit the main repo before its dependencies so that you always get a valid state stored under version control.
-
-If you want to add another dependency later on, you can run `multi add ../NewDependency` and you can do the opposite with `multi remove ../SomeOtherDependency`.
-
-If you want to checkout a previous revision (say `e690d`), you use the checkout command: `multi checkout e690d`. This will checkout the main repo's `e690d` revision and all of its dependencies with the proper revisions in detached HEAD state.
-
-If you want to setup your project on another machine, simply clone the main repo in a container directory (see above) and run `multi install`. This will clone each dependency and checkout the appropriate branches.
-
-If you want to stop using git-multirepo, run `multi uninit`. This will remove all traces of git-multirepo from your repository and working copy.
-
-## Advantages
-
-- Makes setting up the project on a new machine a breeze.
-- Works really well for multiple projects that share a common set of constantly evolving dependencies.
-- Each dependency's repository is totally independent from the main repository, which simplifies a lot of things (merges, contributing upstream, etc.) and works well with git GUIs.
-- While the repositories are independent, git-multirepo makes sure to track everything that's required to bring back a previous version of your project in a valid state.
-- Much more approachable to novice developers than submodules or subtrees.
-- Once setup, there is little need for git-multirepo commands, so you are free to use whatever tools you like to work with your git repos.
-- Low possibility of human error (such as forgetting to contribute dependency changes back to the appropriate remotes, forgetting to commit dependencies before committing the main project, etc.)
-- You're not stuck with git-multirepo. It stores its metadata as [YAML](http://www.yaml.org) in the main repo. You can clone and checkout appropriate revisions of your dependencies by hand without git-multirepo if you need to. The information is there, in human-readable form.
-
-| How It Handles... | git-multirepo | git submodules | git subtrees |
-|----------------------------------|:----------------:|:--------------:|:------------:|
-| Working Copy | beside main repo | in main repo | in main repo |
-| Constantly Evolving Dependencies | easy | hard | passable |
-| Merging Changes to Dependencies | easy | hard | passable |
-| Contributing Upstream | easy | easy | passable |
-| Continuous Integration | medium | medium | easy |
-| Complex Branch-Based Workflows | hard* | hard | easy |
-
-(*) This should get better in future versions of git-multirepo.
-
-## Limitations
-
-- git-multirepo should be considered beta at the moment. All of the core features work as described, though. Suggestions and contributions are welcome.
-- The project and its dependencies must live beside each other on disk (for now).
-- There are currently no features to facilitate branch-heavy workflows.
-- You must (ideally) install the tool on your CI server: `gem install git-multirepo`
-
-## Summary of Commands
-
-Here is a quick rundown of commands available to you in git-multirepo:
-
-| Command | Description |
-|---------|-------------|
-| init | Initialize the current repository as a multirepo project. |
-| add | Track an additional dependency with multirepo. |
-| branch | Create and/or checkout a new branch for all repos. |
-| checkout | Checks out the specified commit or branch of the main repo and checks out matching versions of all dependencies. |
-| edit | Opens the .multirepo file in the default text editor. |
-| fetch | Performs a git fetch on all dependencies. |
-| install | Clones and checks out dependencies as defined in the .multirepo file, and installs git-multirepo's local pre-commit hook. |
-| open | Opens all dependencies in the current OS's file explorer. |
-| remove | Removes the specified dependency from multirepo. |
-| update | Force-updates the multirepo lock file. |
-| uninit | Removes all traces of multirepo in the current multirepo repository. |
-
-## Metadata
-
-git-multirepo stores all of its metadata in two files:
-
-| File | Format | Contents |
-|------|--------|----------|
-| .multirepo | YAML | A collection of your project's dependencies. For each dependency, stores its **local path** relative to the main repo, the **remote URL** and the **branch** your project depends upon.
-| .multirepo.lock | YAML | For each dependency, stores the **commit hash** and **branch** on which the dependency was when the main repo was committed. The dependency's **name** is also included but only serves as a reference to make inspecting the lock file easier. |
-
+![git-multirepo](images/logo.png)
+
+# git-multirepo
+
+[![Gem Version](https://badge.fury.io/rb/git-multirepo.svg)](http://badge.fury.io/rb/git-multirepo)
+
+Track multiple Git repositories side-by-side.
+
+An alternative approach to manage constantly evolving dependencies.
+
+Check out [the project's to-do list](https://www.pivotaltracker.com/n/projects/1256156) to get an idea of upcoming enhancements.
+
+## Motivation
+
+By now the
+[pitfalls](http://somethingsinistral.net/blog/git-submodules-are-probably-not-the-answer/)
+of git submodules are
+[pretty](https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/)
+[well](http://slopjong.de/2013/06/04/git-why-submodules-are-evil/)
+[known](http://stackoverflow.com/questions/12075809/git-submodules-workflow-issues).
+They work when your dependencies are linearly-evolving third-party libraries that you seldom update but they fall apart when it comes to managing your own, constantly evolving dependencies.
+
+Git subtrees are the recommended alternative but have pitfalls of their own:
+
+- They require verbose and error-prone command-line operations. This can become quite tedious when managing more than one or two dependencies.
+- They change the rules of the game when it comes to merges.
+- Each developer has to configure the appropriate remotes and subtrees on his machine if he or she wants to contribute back.
+- Developers must not forget to push changes to dependencies back to the appropriate remotes.
+- Few git GUIs have any kind of subtree integration, so you're stuck with the command-line.
+
+Etc.
+
+## Overview
+
+Using git-multirepo, you can manage your main project and its dependencies as completely independent repositories while still maintaining the ability to checkout a previous revision in a single step and have the project build properly.
+
+A git-multirepo setup looks like this:
+
+```
+MyAwesomeProject
+  |-- AwesomeApp
+  |-- Dependency1
+  |-- Dependency2
+```
+
+In essence:
+
+1. You tell git-multirepo what your dependencies are.
+2. Each time you commit the main repo, git-multirepo tracks what revision of each dependency is required by the project (don't worry, it ensures that you don't forget to commit changes to dependencies beforehand; more on that later).
+3. If you ever want to go back to a previous version of your project, git-multirepo handles checking out the main repo and appropriate revisions of all of its dependencies in a single, seamless operation.
+4. Setting up the project on a new machine is only a single `git clone` and `multi install` away.
+
+## Example
+
+Say you want to track an existing project with git-multirepo:
+
+1. Organize repos on disk in the following manner:
+
+	```
+	MyAwesomeProject
+	  |-- AwesomeApp
+	  |-- Dependency1
+	  |-- Dependency2
+	```
+
+2. `cd` into the *AwesomeApp* directory (aka the "main repo").
+3. Run `multi init`.
+4. You will get prompted to add *Dependency1* and *Dependency2* to multirepo; do so.
+5. git-multirepo reads all required information from dependency repos and initializes itself, storing its metadata files in the main repo, under version control.
+
+From now on, each time you commit the main repo git-multirepo tracks — using a pre-commit hook — which revision of each dependency is required for that main repo revision, and where to get them. The pre-commit hook also ensures that you won't commit the main repo before its dependencies so that you always get a valid state stored under version control.
+
+If you want to add another dependency later on, you can run `multi add ../NewDependency` and you can do the opposite with `multi remove ../SomeOtherDependency`.
+
+If you want to checkout a previous revision (say `e690d`), you use the checkout command: `multi checkout e690d`. This will checkout the main repo's `e690d` revision and all of its dependencies with the proper revisions in detached HEAD state.
+
+If you want to setup your project on another machine, simply clone the main repo in a container directory (see above) and run `multi install`. This will clone each dependency and checkout the appropriate branches.
+
+If you want to stop using git-multirepo, run `multi uninit`. This will remove all traces of git-multirepo from your repository and working copy.
+
+## Advantages
+
+- Makes setting up the project on a new machine a breeze.
+- Works really well for multiple projects that share a common set of constantly evolving dependencies.
+- Each dependency's repository is totally independent from the main repository, which simplifies a lot of things (merges, contributing upstream, etc.) and works well with git GUIs.
+- While the repositories are independent, git-multirepo makes sure to track everything that's required to bring back a previous version of your project in a valid state.
+- Much more approachable to novice developers than submodules or subtrees.
+- Once setup, there is little need for git-multirepo commands, so you are free to use whatever tools you like to work with your git repos.
+- Low possibility of human error (such as forgetting to contribute dependency changes back to the appropriate remotes, forgetting to commit dependencies before committing the main project, etc.)
+- You're not stuck with git-multirepo. It stores its metadata as [YAML](http://www.yaml.org) in the main repo. You can clone and checkout appropriate revisions of your dependencies by hand without git-multirepo if you need to. The information is there, in human-readable form.
+
+| How It Handles... | git-multirepo | git submodules | git subtrees |
+|----------------------------------|:----------------:|:--------------:|:------------:|
+| Working Copy | beside main repo | in main repo | in main repo |
+| Constantly Evolving Dependencies | easy | hard | passable |
+| Merging Changes to Dependencies | easy | hard | passable |
+| Contributing Upstream | easy | easy | passable |
+| Continuous Integration | medium | medium | easy |
+| Complex Branch-Based Workflows | hard* | hard | easy |
+
+(*) This should get better in future versions of git-multirepo.
+
+## Limitations
+
+- git-multirepo should be considered beta at the moment. All of the core features work as described, though. Suggestions and contributions are welcome.
+- The project and its dependencies must live beside each other on disk (for now).
+- There are currently no features to facilitate branch-heavy workflows.
+- You must (ideally) install the tool on your CI server: `gem install git-multirepo`
+
+## Summary of Commands
+
+Here is a quick rundown of commands available to you in git-multirepo:
+
+| Command | Description |
+|---------|-------------|
+| init | Initialize the current repository as a multirepo project. |
+| add | Track an additional dependency with multirepo. |
+| branch | Create and/or checkout a new branch for all repos. |
+| checkout | Checks out the specified commit or branch of the main repo and checks out matching versions of all dependencies. |
+| clone | Clones the specified repository in a subfolder, then install it. |
+| edit | Opens the .multirepo file in the default text editor. |
+| fetch | Performs a git fetch on all dependencies. |
+| install | Clones and checks out dependencies as defined in the .multirepo file, and installs git-multirepo's local pre-commit hook. |
+| open | Opens all dependencies in the current OS's file explorer. |
+| remove | Removes the specified dependency from multirepo. |
+| update | Force-updates the multirepo lock file. |
+| uninit | Removes all traces of multirepo in the current multirepo repository. |
+
+## Metadata
+
+git-multirepo stores all of its metadata in two files:
+
+| File | Format | Contents |
+|------|--------|----------|
+| .multirepo | YAML | A collection of your project's dependencies. For each dependency, stores its **local path** relative to the main repo, the **remote URL** and the **branch** your project depends upon.
+| .multirepo.lock | YAML | For each dependency, stores the **commit hash** and **branch** on which the dependency was when the main repo was committed. The dependency's **name** is also included but only serves as a reference to make inspecting the lock file easier. |
+
 The information contained in .multirepo and .multirepo.lock allow one-step cloning of a project and all its dependencies, and checking out any prior revision of the main project with appropriate revisions of all of its dependencies, respectively.