commit 7e1c2d8f4816ad1e6b00c01128d8d49bf109a4cd parent 166dbaa8564f614ecc613c12a587ef602d0b190e Author: Eamon Caddigan <eamon.caddigan@gmail.com> Date: Wed, 4 Dec 2024 07:40:33 -0800 Update Git post with new links Diffstat:
| M | content/posts/git-links/index.md | | | 18 | +++++++++++++++++- |
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/content/posts/git-links/index.md b/content/posts/git-links/index.md @@ -1,7 +1,7 @@ --- title: "Useful and interesting Git posts" date: 2024-02-11T20:00:20-08:00 -lastmod: 2024-11-16T15:28:48-08:00 +lastmod: 2024-12-04T07:23:18-08:00 description: "This is just a collection of interesting (and not necessarily recent) Git posts from around the web. I will update this as I find new things." draft: false categories: @@ -71,3 +71,19 @@ post on why and how to craft commit messages. This post introduced me to the commit subjects. I.e., “a properly formed Git commit subject line should always be able to complete the following sentence: ‘If applied, this commit will _your subject line here_’.” + +## Intermediate Usage Tips + +[George Brocklehurst --- Auto-squashing Git +Commits](https://thoughtbot.com/blog/autosquashing-git-commits) + +I didn’t really get on board with a rebase-based workflow until I learned +about autosquashing. I now always run `git config --global rebase.autosquash +true` when I’m setting up a new account. + +[Adam Johnson --- Force push safely with `--force-with-lease` and +`--force-if-includes`](https://adamj.eu/tech/2023/10/31/git-force-push-safely/) + +I was unaware of these options before I saw this post. I still hardly use +them---I’m still not sure if it’s a good idea to force push to a remote most +of the time---but if you’re going to do it you ought to include these.