From bb7b112d49a768d8fd5a32f0d78549d05549d15a Mon Sep 17 00:00:00 2001 From: mattmc3 Date: Wed, 3 Jul 2024 09:40:19 -0400 Subject: [PATCH] Fix format --- content/posts/2024-07-03-better-git-shell-aliases.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/2024-07-03-better-git-shell-aliases.md b/content/posts/2024-07-03-better-git-shell-aliases.md index a5e832f..f06bda9 100644 --- a/content/posts/2024-07-03-better-git-shell-aliases.md +++ b/content/posts/2024-07-03-better-git-shell-aliases.md @@ -57,7 +57,7 @@ They also wouldn't need to risk modifying people's gitconfigs every time Oh-My-Z By now you can probably see where this is going - these kinds of complex inline git aliases are an antipattern. My `gitconfig` was a mess of shell scripts I could not easily read or understand. Add to that the problem of mixing code and configuration in one file. For the occasional one-off, sure. Fine. Do whatever. But once I got past a certain number of these aliases at a certain complexity, it was time to refactor. > _Code should live in a place where it's easy to evaluate, execute, and evolve, not in some config strings where you can't do any of those things_. -> - me, having a shower thought +> \- me, having a shower thought ## My solution