croxton/Stash — pull request #95 by timkelty (2014-02-24 17:37:01+00:00)
Title: Add Composer compatibility

Ideally, you'd have it on Packagist: https://packagist.org/about and set up a GitHub service hook so it updated every time you pushed.

That's not necessary however, even with just the composer.json file, users could manually put in the git repo like so:
```json
{
"require": {
"croxton/stash": "2.5.*@dev"
},
{
"type": "vcs",
"url": "https://github.com/croxton/Stash.git"
}
],
"config": {
"vendor-dir": "vendor/composer"
},
"minimum-stability": "dev"
}
```

Another note - The alias of "dev-dev" might look funny. Generally this is "dev-master", assuming master is the "newest" branch, and the developer is using some sort of "stable" branch, In your case, you're using master for stable and dev for latest, hence "dev-dev". The purpose of the alias is so that a user can just reference dev-master (or dev-dev) in your case and always get the latest regardless of vcs bumps.