Support single and multi repo setup & make setup more user-friendly #2
Conversation
…dkopp/termux-scripts into support-single-and-multi-repo-setup
davidkopp changed the title 
| @abatkin With this PR I have changed the setup scripts significantly. I would be happy to know if the scripts still cover your use case or if there are additional changes necessary. |
There was a problem hiding this comment.
I think it would work as-is (except the -d check) and I will try it out soon. I also left some other comments that might simplify setup (and make it clearer that in multi-repo setups, repo.conf should not be present, since otherwise you'll end up with an unused copy with whatever values happen to be present after the final invocation of setup-git-repo.sh).
| } | ||
| | ||
| cd $HOME/storage/shared/$GH_REPO | ||
| echo -e "Setup Git repository\n" |
There was a problem hiding this comment.
Prompting the user is interesting. If you didn't want to do that, another way to do it would be to check if repo.conf exists, and if it does, blindly use that. If it does not exist, ensure that the user passes in a path to a git repository (and optionally a branch name) and then trust that the user will also be passing in the path to Tasker, since no repo.conf file exists.
There was a problem hiding this comment.
Hmm, this also prompts the user so that the script can clone the repository if the user hasn't already done it. That's neat. Maybe if the repository directory doesn't exist, that's when you can prompt them?
Breaking changes:
repo.confthroughGH_REPOhas changed from relative path to an absolute path and it was renamed toGIT_REPO_PATH. Example:GIT_REPO_PATH=~/storage/shared/git/notesChanges: