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.63d82a82-4f85-440b-85d6-8c6a0cd0b5d9.json
View file

@ -82,9 +82,9 @@
],
"body": [
{
"value": "\n <p>Sometimes when <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2025\/02\/11\/tidy\">tidying my commits<\/a> or updating a local branch with remote changes, the order of commits changes - making them out of order in when running <code>git log<\/code>.<\/p>\n\n<p>I want the commits in the log to be in the correct sequential order.<\/p>\n\n<p>If not, it would be confusing if I review the commits in the future.<\/p>\n\n<p>This is easy to fix when running <code>git rebase -i<\/code> to perform an interactive rebase on the commits.<\/p>\n\n<p>The commit has a <code>-x<\/code> or <code>--exec<\/code> option that will perform a given command on each commit.<\/p>\n\n<p>The commit date can be reset using <code>git reset --amend<\/code>, and combining these commands will amend the date of each commit.<\/p>\n\n<p>Running <code>git rebase --interactive --exec \"git commit --amend --no-edit --date now\"<\/code> will amend and update each commit, keeping the commit message the same, but changing the commit date to the current time - leaving the Git log in the correct order.<\/p>\n\n ",
"value": "\n <p>Sometimes when <a href=\"/daily\/2025\/02\/11\/tidy\">tidying my commits<\/a> or updating a local branch with remote changes, the order of commits changes - making them out of order in when running <code>git log<\/code>.<\/p>\n\n<p>I want the commits in the log to be in the correct sequential order.<\/p>\n\n<p>If not, it would be confusing if I review the commits in the future.<\/p>\n\n<p>This is easy to fix when running <code>git rebase -i<\/code> to perform an interactive rebase on the commits.<\/p>\n\n<p>The commit has a <code>-x<\/code> or <code>--exec<\/code> option that will perform a given command on each commit.<\/p>\n\n<p>The commit date can be reset using <code>git reset --amend<\/code>, and combining these commands will amend the date of each commit.<\/p>\n\n<p>Running <code>git rebase --interactive --exec \"git commit --amend --no-edit --date now\"<\/code> will amend and update each commit, keeping the commit message the same, but changing the commit date to the current time - leaving the Git log in the correct order.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p>Sometimes when <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2025\/02\/11\/tidy\">tidying my commits<\/a> or updating a local branch with remote changes, the order of commits changes - making them out of order in when running <code>git log<\/code>.<\/p>\n\n<p>I want the commits in the log to be in the correct sequential order.<\/p>\n\n<p>If not, it would be confusing if I review the commits in the future.<\/p>\n\n<p>This is easy to fix when running <code>git rebase -i<\/code> to perform an interactive rebase on the commits.<\/p>\n\n<p>The commit has a <code>-x<\/code> or <code>--exec<\/code> option that will perform a given command on each commit.<\/p>\n\n<p>The commit date can be reset using <code>git reset --amend<\/code>, and combining these commands will amend the date of each commit.<\/p>\n\n<p>Running <code>git rebase --interactive --exec \"git commit --amend --no-edit --date now\"<\/code> will amend and update each commit, keeping the commit message the same, but changing the commit date to the current time - leaving the Git log in the correct order.<\/p>\n\n ",
"processed": "\n <p>Sometimes when <a href=\"/daily\/2025\/02\/11\/tidy\">tidying my commits<\/a> or updating a local branch with remote changes, the order of commits changes - making them out of order in when running <code>git log<\/code>.<\/p>\n\n<p>I want the commits in the log to be in the correct sequential order.<\/p>\n\n<p>If not, it would be confusing if I review the commits in the future.<\/p>\n\n<p>This is easy to fix when running <code>git rebase -i<\/code> to perform an interactive rebase on the commits.<\/p>\n\n<p>The commit has a <code>-x<\/code> or <code>--exec<\/code> option that will perform a given command on each commit.<\/p>\n\n<p>The commit date can be reset using <code>git reset --amend<\/code>, and combining these commands will amend the date of each commit.<\/p>\n\n<p>Running <code>git rebase --interactive --exec \"git commit --amend --no-edit --date now\"<\/code> will amend and update each commit, keeping the commit message the same, but changing the commit date to the current time - leaving the Git log in the correct order.<\/p>\n\n ",
"summary": null
}
],