My apologies if I misunderstand this functionality. I am currently playing around with the VCS API module and still not quite sure what it actually does. My question concerns the VCS accounts: Is the module actually supposed to provide access to the repository (in my case, a SVN repository)? If not, what does it do?

I created a SVN repo and registered it under Project administration -> VCS Repositories. Next, I called up versioncontrol/register and registered a VCS account, which was subsequently connected to the current user and the fomerly mentioned SVN repo. It shows up when displaying "My account". But what does it do? What have I achieved?

Comments

jpetso’s picture

jpetso commented
Status: Active » Fixed

VCS accounts are supposed to provide access to the repository, but that currently only works for CVS if you set it up this way. I had a look at this issue and the takeaway is that the current way to export accounts does not map well to version control systems other than CVS, which means that the Version Control API will have to be refined on before the SVN, Git, Mercurial and Bazaar backends can integrate with the respective authentication mechanisms.

So for the time being, user accounts for non-CVS backends are just a way to replace the VCS usernames with the actual Drupal username (including a link to the user page).

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.