Gabriel Nützi
Gabriel Nützi
I am just trying this out, ;-). See #86 This opt-in feature should to 95% be the version we should head towards, having a release checkout in the install folder......
This will be somehow similarly supported with #86: You install with `curl .../install.sh --release-clone-url "" --release-clone-branch "my-super-duper-setup"` which will make a clone in `$INSTALL_DIR/release`. If you make changes in there,...
@rycus86 Please see my last comment in #86
> I just left a review on #92. While reviewing, I noticed some other things, which probably related more to #86, or are otherwise possible improvements of the current code,...
One thing about hooks leaving in place an such is also the thing about the git LFS hooks, they get installed by git directly. These are 100% crucial. If you...
Hmm, right now I am thinking if we dont have the single install stuff anymore: **why not only use core.hooksPath** for all cases. ** no templates. Wouldnt that be possible?...
Ok, thanks for the summary and reasoning @rycus86. IMO: both are valuable. @matthijskooijman : LFS hooks are completey supported by githooks it self. They get move and disabled if detected...
@matthijskooijman : Awesome: Actually with #111 , I have now added a folder `hooks` to the repo with all hooks (modified `base-template-symlink.sh`) git supports. In this way a simple install...
Maybe its just "wincrap" and its bash... Maybe our changes with dispatching with `exec` and so forth.... dunno
https://stackoverflow.com/questions/58473685/sending-sigint-to-forked-exec-process-which-runs-script-does-not-kill-it