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.fe407991-a896-410c-9223-51a7ad43d4d2.json
View file

@ -82,9 +82,9 @@
],
"body": [
{
"value": "\n <p><a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/10\/24\/git-stash-is-underrated\">In yesterday's email<\/a> where I wrote about <code>git stash<\/code>, I mentioned the <code>-p<\/code> or <code>--patch<\/code> options.<\/p>\n\n<p>When stashing changes, this allows you to interactively select which changes you want to stash and what you don't.<\/p>\n\n<p>This is supported by other Git commands, including <code>git add<\/code>.<\/p>\n\n<p>I always use <code>git add -p<\/code> when adding changes as it gives me the chance to review them before committing them.<\/p>\n\n<p>If I left any stray comments, debug code, trailing spaces or anything I don't want to commit, I can remove them.<\/p>\n\n<p>If I was working on multiple changes (which I avoid), I can select the appropriate changes and create commits related to each change to keep the history clean and useful.<\/p>\n\n<p>I also use <code>git diff<\/code> and <code>git diff --staged<\/code> to review changes as well as <code>git show<\/code> to review commits.<\/p>\n\n<p>By doing this, I know my commits will be in the best state for others to review now or for me to review if I need to in the future.<\/p>\n\n ",
"value": "\n <p><a href=\"/daily\/2024\/10\/24\/git-stash-is-underrated\">In yesterday's email<\/a> where I wrote about <code>git stash<\/code>, I mentioned the <code>-p<\/code> or <code>--patch<\/code> options.<\/p>\n\n<p>When stashing changes, this allows you to interactively select which changes you want to stash and what you don't.<\/p>\n\n<p>This is supported by other Git commands, including <code>git add<\/code>.<\/p>\n\n<p>I always use <code>git add -p<\/code> when adding changes as it gives me the chance to review them before committing them.<\/p>\n\n<p>If I left any stray comments, debug code, trailing spaces or anything I don't want to commit, I can remove them.<\/p>\n\n<p>If I was working on multiple changes (which I avoid), I can select the appropriate changes and create commits related to each change to keep the history clean and useful.<\/p>\n\n<p>I also use <code>git diff<\/code> and <code>git diff --staged<\/code> to review changes as well as <code>git show<\/code> to review commits.<\/p>\n\n<p>By doing this, I know my commits will be in the best state for others to review now or for me to review if I need to in the future.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p><a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/10\/24\/git-stash-is-underrated\">In yesterday's email<\/a> where I wrote about <code>git stash<\/code>, I mentioned the <code>-p<\/code> or <code>--patch<\/code> options.<\/p>\n\n<p>When stashing changes, this allows you to interactively select which changes you want to stash and what you don't.<\/p>\n\n<p>This is supported by other Git commands, including <code>git add<\/code>.<\/p>\n\n<p>I always use <code>git add -p<\/code> when adding changes as it gives me the chance to review them before committing them.<\/p>\n\n<p>If I left any stray comments, debug code, trailing spaces or anything I don't want to commit, I can remove them.<\/p>\n\n<p>If I was working on multiple changes (which I avoid), I can select the appropriate changes and create commits related to each change to keep the history clean and useful.<\/p>\n\n<p>I also use <code>git diff<\/code> and <code>git diff --staged<\/code> to review changes as well as <code>git show<\/code> to review commits.<\/p>\n\n<p>By doing this, I know my commits will be in the best state for others to review now or for me to review if I need to in the future.<\/p>\n\n ",
"processed": "\n <p><a href=\"/daily\/2024\/10\/24\/git-stash-is-underrated\">In yesterday's email<\/a> where I wrote about <code>git stash<\/code>, I mentioned the <code>-p<\/code> or <code>--patch<\/code> options.<\/p>\n\n<p>When stashing changes, this allows you to interactively select which changes you want to stash and what you don't.<\/p>\n\n<p>This is supported by other Git commands, including <code>git add<\/code>.<\/p>\n\n<p>I always use <code>git add -p<\/code> when adding changes as it gives me the chance to review them before committing them.<\/p>\n\n<p>If I left any stray comments, debug code, trailing spaces or anything I don't want to commit, I can remove them.<\/p>\n\n<p>If I was working on multiple changes (which I avoid), I can select the appropriate changes and create commits related to each change to keep the history clean and useful.<\/p>\n\n<p>I also use <code>git diff<\/code> and <code>git diff --staged<\/code> to review changes as well as <code>git show<\/code> to review commits.<\/p>\n\n<p>By doing this, I know my commits will be in the best state for others to review now or for me to review if I need to in the future.<\/p>\n\n ",
"summary": null
}
],