Composer Testing and Debugging Plugins

Question

I am developing my own installer for the linker for proprietary software, and I'm not quite sure how I should test and debug it.

Composer only downloads plugins if it is specified as a dependency, so I am creating a test project that defines the plugin as a dependency, for example:

{
    //...
    "repositories": [
        {
            "type":"git",
            "url":"/path/to/gitrepo"
        }
    ],
    "require":{
        "myvendor/my-plugin":"dev-master"
    }
}

The problem is that the composer uses only the latest perfect version, which means that if I want to check something, I must first fix it. This leads to a lot of “useless” changes on one line (like “oh, I forgot the comma there”), which I really don't want to have a git repo in my history.

, , . ( ), , "".

Answer 1

. , , . s . . fooobar.com/questions/78694/... .

.

. :

Answer 2

tags --force push -. -

{
    //...
    "repositories": [
        {
            "type":"git",
            "url":"/path/to/gitrepo"
        }
    ],
    "require":{
        "myvendor/my-plugin":"dev-tag"
    }
}

, , dev-tag,

git push origin master --force --tags

, .

composer update

.

, !