Development life-cycle for extensions (with Composer)

Hi all,

I have a few Yii projects that rely on a lot of the same code I’ve developed, so I’ve bundled this up into an a few extensions.

The issue I have now is that I have separate repositories for each extension, and then a repository for my main application, and I include my extensions into my main application using Composer.

This requires me to maintain my extension outside of my current application, and I have to commit all changes before I can then do a ‘composer update’ within my application to see the changes.

Ideally I want to have a way of working locally and having an alias to the local working copy of my extension while I do development, and then switch to a remote/GitHub copy once I’ve finished a version of the application.

How does everyone else manage this?

Dan