-
-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Git Remote to be reconfigured #36
Comments
Hi, Or is there a way to change the default "notes" folder of GitJournal. I need to do this so it plays nicely with my other linux desktop app. For example if I have ~/notes/ on my desktop everything works fine. But I need to have ~/notes/default/ and I want to make "default" the default folder for gitjournal. It still works as is, but basically I can only see notes in the folder view. The notes view is always empty. Thanks |
Downvoting in earnest since I think this thing is ultimately important but hardly important for early adopters. We can just reinstall the app. Thanks for building gitjournal! |
This is quick and dirty way of fixing the problem. It doesn't migrate the notes from the previous repo and just discards them, so you cannot move your notes from one repo to another using GitJournal (for now), but at least its better than having to re-install the app. Related to #36
The current solution allows you to clone a different repository. So it's not exactly letting you configure the git remotes, but it's better than nothing. In the future, I'll add a way to change the remote, thereby preserving the data, and maybe even allow multiple remotes. |
Ideally when removing a folder one shouldn't have any notes, but sometimes we do allow an entire folder to be reset. Related to #36
Closing this as there are 2 different bugs to allow an extra remote to be added and to add support for multiple repos. |
Currently once the Git Remote Host has been setup there is no way to change it, or even view what it was set to. We should provide a way to change the remote host, specially since we're a big advocate of Data Portability.
The text was updated successfully, but these errors were encountered: