[BLUEJ-776] Git support does not work properly with file: protocol (or others w/o password?)
It looks like there is an assumption in our teamwork provider that if there is no password set, we must pop up the settings dialog to ask for one before attempting version control actions. But there are several cases where a password is unnecessary, for example with a file: protocol in Git, or checking out of a public read-only repository on HTTP, or over SSH when using private keys. It seems to me that the password assumption needs revisiting. (And I think this also affects SVN?)
Or maybe I misunderstand something in the workings but certainly on BlueJ 4.0.0preview2 RC1, using a file: protocol for Git is not really practical as it pops up the settings dialog whenever you attempt the status action.
Issue metadata
- Issue type: Bug
- Priority: Medium