vba - How to manage a local git repository using Rubberduck -

i'm using rubberduck (version 2.0.13) in combination local git repository version control of vba project.

currently, need re-open repository every time start rubberduck using manage -> open existing repository in source control window.

is there better way handle local repository, e.g. can rubberduck save setting? don't want use online repository, think "unsynced commits" tab irrelevant me.

this started comment, got long... figured i'd make disappointing answer instead.

i don't vba (lately anyway) can't actively use rubberduck's source control feature, , haven't contributed that part, know users seem manage use - both local , remote repositories: these users can give better answer can far using it goes.

there are quite number of open issues involving source control feature, a project dedicated stabilizing it. it's provided "as-is", in "better nothing".

the idea it's supposed pick projectid (which we're storing in write-enabled vbproject.helpfile no-one-ever-uses-that property - want confuse heck out of rubberduck change value) of active project, after we've parsed it, we're sure project has id when in %appdata%\rubberduck\sourcecontrol.rubberduck file see if project id associated known repository - , if that's case, we'd open repository , update sc panel.

the configuration file looks this:

<?xml version="1.0" encoding="utf-8"?> <configuration>   <sourcecontrolsettings>     <username />     <emailaddress />     <defaultrepositorylocation />     <repositories>       <repository>         <id>86689642</id>         <locallocation>c:\dev\vba\vbtools</locallocation>         <remotelocation />       </repository>     </repositories>     <commandpromptlocation>cmd.exe</commandpromptlocation>   </sourcecontrolsettings> </configuration> 

we are storing information - repository <id> should used this, either it's working not reliably, or creating problems , disabled.

but correct: having manually open working repository every time isn't ideal ux. whether there's remote or not shouldn't make difference, still need have local copy when have remote.

i remember @ 1 point debated whether should let user browse repository location, or list known repositories configuration file - decided letting user browse , open git repository known rubberduck or not, make easier , flexible, when no repository known rubberduck yet; feel free open issue on github if have ideas or feature requests (or report bug).