pyratelog

personal blog
git clone git://git.pyratebeard.net/pyratelog.git
Log | Files | Refs | README

commit 2f0131b20634ec88c1d402e80b14b0518b801bfd
parent 04bc045017706c6b730cfa9449cb45292b418f3b
Author: pyratebeard <root@pyratebeard.net>
Date:   Fri, 11 Nov 2022 21:00:12 +0000

what_the_hook

Diffstat:
Mentry/what_the_hook.md | 6+++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/entry/what_the_hook.md b/entry/what_the_hook.md @@ -1,8 +1,8 @@ -Git [hooks](TK){target="_blank" rel="noreferrer"} are often overlooked or underused. They can be very useful, and even used as a rudimentary CI/CD workflow. +Git [hooks](https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks){target="_blank" rel="noreferrer"} are often overlooked or underused. They can be very useful, and even used as a rudimentary CI/CD workflow. While these tips can work for any repo, this could be viewed as an expansion on my [tech_grimoire](20220525-tech_grimoire.html){target="_blank" rel="noreferrer"} post. -For note taking I make use of the [VimWiki](TK){target="_blank" rel="noreferrer"} plugin to Vim. My wiki directory is a git repository, which is then cloned on to one of my servers and using [Gollum](TK){target="_blank" rel="noreferrer"} is available as a website. +For note taking I make use of the [VimWiki](https://vimwiki.github.io/){target="_blank" rel="noreferrer"} plugin to Vim. My wiki directory is a git repository, which is then cloned on to one of my servers and using [Gollum](https://github.com/gollum/gollum){target="_blank" rel="noreferrer"} is available as a website. This has worked well for years, but one thing I have not been good at is committing and pushing changes straight away. In order to improve my workflow I make use of two git hooks, one in the local repo and one in the remote bare repo. @@ -69,4 +69,4 @@ git config core.hooksPath .githooks As far as I am aware there is no way to track hooks in a remote bare repo. If you know of a way I would be interested to hear about it. -Who needs a convoluted CI/CD pipeline when a couple of one line scripts will do. Typing `:Gac` is easy enough that my wiki should now stay up to date. +Who needs a convoluted CI/CD pipeline when a couple of one line scripts will do? Typing `:Gac` is easy enough that my wiki should now stay up to date.