opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

Make all links relative

Browse source 
Now the abs_to_rel module is enabled, links can be made relative so they
work on the current environment.
This commit is contained in:
Oliver Davies 2025-05-29 16:42:25 +01:00
parent 0d359f81d6
commit 7a7dc297ca
349 changed files with 698 additions and 698 deletions
Download patch file Download diff file Expand all files Collapse all files

4
content/node.aba40c6c-363c-489a-b1d3-b0ac5a5890bf.json
View file

@ -82,9 +82,9 @@
],
"body": [
{
"value": "\n <p>There are many good resources and interesting articles online about how to write good messages when committing changes to a Git repository.<\/p>\n\n<p>The post I often refer to is <a href=\"https:\/\/cbea.ms\/git-commit\">How to Write a Git Commit Message<\/a> by Chris Beams.<\/p>\n\n<p>In his post, he explains why good commit messages matter and gives these seven rules:<\/p>\n\n<blockquote>\n <ul>\n <li>Separate the subject from body with a blank line.<\/li>\n <li>Limit the subject line to 50 characters.<\/li>\n <li>Capitalize the subject line.<\/li>\n <li>Do not end the subject line with a period.<\/li>\n <li>Use the imperative mood in the subject line.<\/li>\n <li>Wrap the body at 72 characters.<\/li>\n <li>Use the body to explain what and why vs. how.<\/li>\n <\/ul>\n<\/blockquote>\n\n<p>I'd recommend reading the article to get the full context.<\/p>\n\n<p>Rules two and six suggest lengths for the subject line and body which is another reason <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2025\/04\/02\/commit\">why I rarely use <code>-m<\/code><\/a> when committing changes.<\/p>\n\n<p>Whilst you can create multi-line commit messages on the command line, by opening it in my preferred editor (Neovim for me), I can see where the lines should end and be warned if I exceed them.<\/p>\n\n<p>I can even include Chris' rules in my commit message template so I see them whenever I'm about to commit something.<\/p>\n\n<p>This additional feedback helps me create my commit messages how I intend.<\/p>\n\n ",
"value": "\n <p>There are many good resources and interesting articles online about how to write good messages when committing changes to a Git repository.<\/p>\n\n<p>The post I often refer to is <a href=\"https:\/\/cbea.ms\/git-commit\">How to Write a Git Commit Message<\/a> by Chris Beams.<\/p>\n\n<p>In his post, he explains why good commit messages matter and gives these seven rules:<\/p>\n\n<blockquote>\n <ul>\n <li>Separate the subject from body with a blank line.<\/li>\n <li>Limit the subject line to 50 characters.<\/li>\n <li>Capitalize the subject line.<\/li>\n <li>Do not end the subject line with a period.<\/li>\n <li>Use the imperative mood in the subject line.<\/li>\n <li>Wrap the body at 72 characters.<\/li>\n <li>Use the body to explain what and why vs. how.<\/li>\n <\/ul>\n<\/blockquote>\n\n<p>I'd recommend reading the article to get the full context.<\/p>\n\n<p>Rules two and six suggest lengths for the subject line and body which is another reason <a href=\"/daily\/2025\/04\/02\/commit\">why I rarely use <code>-m<\/code><\/a> when committing changes.<\/p>\n\n<p>Whilst you can create multi-line commit messages on the command line, by opening it in my preferred editor (Neovim for me), I can see where the lines should end and be warned if I exceed them.<\/p>\n\n<p>I can even include Chris' rules in my commit message template so I see them whenever I'm about to commit something.<\/p>\n\n<p>This additional feedback helps me create my commit messages how I intend.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p>There are many good resources and interesting articles online about how to write good messages when committing changes to a Git repository.<\/p>\n\n<p>The post I often refer to is <a href=\"https:\/\/cbea.ms\/git-commit\">How to Write a Git Commit Message<\/a> by Chris Beams.<\/p>\n\n<p>In his post, he explains why good commit messages matter and gives these seven rules:<\/p>\n\n<blockquote>\n <ul>\n <li>Separate the subject from body with a blank line.<\/li>\n <li>Limit the subject line to 50 characters.<\/li>\n <li>Capitalize the subject line.<\/li>\n <li>Do not end the subject line with a period.<\/li>\n <li>Use the imperative mood in the subject line.<\/li>\n <li>Wrap the body at 72 characters.<\/li>\n <li>Use the body to explain what and why vs. how.<\/li>\n <\/ul>\n<\/blockquote>\n\n<p>I'd recommend reading the article to get the full context.<\/p>\n\n<p>Rules two and six suggest lengths for the subject line and body which is another reason <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2025\/04\/02\/commit\">why I rarely use <code>-m<\/code><\/a> when committing changes.<\/p>\n\n<p>Whilst you can create multi-line commit messages on the command line, by opening it in my preferred editor (Neovim for me), I can see where the lines should end and be warned if I exceed them.<\/p>\n\n<p>I can even include Chris' rules in my commit message template so I see them whenever I'm about to commit something.<\/p>\n\n<p>This additional feedback helps me create my commit messages how I intend.<\/p>\n\n ",
"processed": "\n <p>There are many good resources and interesting articles online about how to write good messages when committing changes to a Git repository.<\/p>\n\n<p>The post I often refer to is <a href=\"https:\/\/cbea.ms\/git-commit\">How to Write a Git Commit Message<\/a> by Chris Beams.<\/p>\n\n<p>In his post, he explains why good commit messages matter and gives these seven rules:<\/p>\n\n<blockquote>\n <ul>\n <li>Separate the subject from body with a blank line.<\/li>\n <li>Limit the subject line to 50 characters.<\/li>\n <li>Capitalize the subject line.<\/li>\n <li>Do not end the subject line with a period.<\/li>\n <li>Use the imperative mood in the subject line.<\/li>\n <li>Wrap the body at 72 characters.<\/li>\n <li>Use the body to explain what and why vs. how.<\/li>\n <\/ul>\n<\/blockquote>\n\n<p>I'd recommend reading the article to get the full context.<\/p>\n\n<p>Rules two and six suggest lengths for the subject line and body which is another reason <a href=\"/daily\/2025\/04\/02\/commit\">why I rarely use <code>-m<\/code><\/a> when committing changes.<\/p>\n\n<p>Whilst you can create multi-line commit messages on the command line, by opening it in my preferred editor (Neovim for me), I can see where the lines should end and be warned if I exceed them.<\/p>\n\n<p>I can even include Chris' rules in my commit message template so I see them whenever I'm about to commit something.<\/p>\n\n<p>This additional feedback helps me create my commit messages how I intend.<\/p>\n\n ",
"summary": null
}
],