dev-develop branch breaks composer

matteosister / GitElephant

An abstraction layer for git written in PHP

GNU Lesser General Public License v3.0

613 stars 74 forks source link

dev-develop branch breaks composer #137

Closed geek-merlin closed 6 years ago

geek-merlin commented 6 years ago

How to reproduce:

build a composer project where one package requires gitelephant:^1.0 and another requires gitelephant:dev-develop

Result:

Your requirements could not be resolved to an installable set of packages.

How to fix: Rename develop branch to 1.x

Dunno if there's alternative composer-fu for that.

geek-merlin commented 6 years ago

And here's the link to the composer-fu: https://getcomposer.org/doc/articles/aliases.md#branch-alias

GenieTim commented 6 years ago

The version constraint ^1.0 does not correspond to the branch name but rather the git tag. It is not recommended, to set the version to a branch, especially not dev-develop. Either change dev-develop to dev-master, as the tags are set on the master branch, or open an issue at the repo of the dependency which requires gitelephant at dev-develop.