Rob

Hence my alternative solution; ``` repositories: [ { "type": "vcs", "url": "http://svn.example.org/projectA/", "branches-path": "branches/development" }, { "type": "vcs", "url": "http://svn.example.org/projectA/", "branches-path": "branches/releases" } ] ```

@xylesoft you would have to submit the pull request to [composer/composer](/composer/composer). I think it would have merit. Not many people still use SVN, but for those that do it might...

Isn't this already possible? /cc @Seldaek

I honestly forgot pretty much everything I knew about SVN. It has been over 6 years since I last used it. So not sure I can be of any help...

Satis is entirely maintained and developed by volunteers and open source contributors. It is not actively developed by the Composer core team. We encourage everyone to submit PRs and we...

It is not supposed to be in this file.

Try running: ``` composer config -g gitlab-oauth. ``` replace `` with the full domain (including subdomain) to your repository. replace `` with a valid oauth token (not personal access token).

Because that documentation is for using Satis from within a Composer project. It is not about configuration for Satis itself. The `options` array is supported by the repository type `composer`...

Satis is not explicitly locked to `1.2.1`. It has a constraint that allows higher versions. We just don't update the lock file unless there are other changes as well. You...

> Same probleme with my private gitweb, generated link looks like `https://mygit.com/my-package.git` > as should be `https://mygit.com/?p=my-package.git;a=summary` > > Is there a way to configure an link url mask ?...