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

tome export

Browse source
This commit is contained in:
Oliver Davies 2025-05-30 02:14:32 +01:00
parent 52278c3a53
commit 7a52afab5f
960 changed files with 3670 additions and 2229 deletions
Download patch file Download diff file Expand all files Collapse all files

6
content/node.d0cabfc7-0a42-4d21-a028-eb1220bfece8.json
View file

@ -82,15 +82,15 @@
],
"body": [
{
"value": "\n <p><a href=\"/daily\/2024\/05\/17\/why-i-dont-commit-with--m\">Yesterday<\/a>, I mentioned the 50\/72 rule when writing Git commit messages.<\/p>\n\n<p>The first line in the commit message is the subject line and should be no longer than 50 characters.<\/p>\n\n<p>Any additional lines are the message body and should be wrapped at 72 characters.<\/p>\n\n<p>As I said, I have Neovim configured to format my commit messages based on these rules, although they're more like guidelines.<\/p>\n\n<p>There's no hard limit on the number of characters in the subject line or the number of characters in the body.<\/p>\n\n<p>The commit will work and not be rejected when pushing to your remote repository.<\/p>\n\n<p>There are likely post-commit <a href=\"/daily\/2022\/08\/16\/what-are-git-hooks-why-are-they-useful\">Git hooks<\/a> to do this, but by default, things will work.<\/p>\n\n<p>A commit message to Drupal core today was 178 characters long, including the issue ID and contributors.<\/p>\n\n<p>When working on project teams, ideally, everyone would follow the 50\/72 rule, but if they don't consistently, I don't think it's an issue.<\/p>\n\n<p>I'd rather they focused on writing a good and descriptive commit message and if it's formatted correctly, that's a bonus.<\/p>\n\n<p>Whilst I could automate checks for this, I don't think it's the best use of everyone's time and, especially for Junior Developers who already have enough to learn already, not where their focus should be.<\/p>\n\n ",
"value": "\n <p><a href=\"\/daily\/2024\/05\/17\/why-i-dont-commit-with--m\">Yesterday<\/a>, I mentioned the 50\/72 rule when writing Git commit messages.<\/p>\n\n<p>The first line in the commit message is the subject line and should be no longer than 50 characters.<\/p>\n\n<p>Any additional lines are the message body and should be wrapped at 72 characters.<\/p>\n\n<p>As I said, I have Neovim configured to format my commit messages based on these rules, although they're more like guidelines.<\/p>\n\n<p>There's no hard limit on the number of characters in the subject line or the number of characters in the body.<\/p>\n\n<p>The commit will work and not be rejected when pushing to your remote repository.<\/p>\n\n<p>There are likely post-commit <a href=\"\/daily\/2022\/08\/16\/what-are-git-hooks-why-are-they-useful\">Git hooks<\/a> to do this, but by default, things will work.<\/p>\n\n<p>A commit message to Drupal core today was 178 characters long, including the issue ID and contributors.<\/p>\n\n<p>When working on project teams, ideally, everyone would follow the 50\/72 rule, but if they don't consistently, I don't think it's an issue.<\/p>\n\n<p>I'd rather they focused on writing a good and descriptive commit message and if it's formatted correctly, that's a bonus.<\/p>\n\n<p>Whilst I could automate checks for this, I don't think it's the best use of everyone's time and, especially for Junior Developers who already have enough to learn already, not where their focus should be.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p><a href=\"/daily\/2024\/05\/17\/why-i-dont-commit-with--m\">Yesterday<\/a>, I mentioned the 50\/72 rule when writing Git commit messages.<\/p>\n\n<p>The first line in the commit message is the subject line and should be no longer than 50 characters.<\/p>\n\n<p>Any additional lines are the message body and should be wrapped at 72 characters.<\/p>\n\n<p>As I said, I have Neovim configured to format my commit messages based on these rules, although they're more like guidelines.<\/p>\n\n<p>There's no hard limit on the number of characters in the subject line or the number of characters in the body.<\/p>\n\n<p>The commit will work and not be rejected when pushing to your remote repository.<\/p>\n\n<p>There are likely post-commit <a href=\"/daily\/2022\/08\/16\/what-are-git-hooks-why-are-they-useful\">Git hooks<\/a> to do this, but by default, things will work.<\/p>\n\n<p>A commit message to Drupal core today was 178 characters long, including the issue ID and contributors.<\/p>\n\n<p>When working on project teams, ideally, everyone would follow the 50\/72 rule, but if they don't consistently, I don't think it's an issue.<\/p>\n\n<p>I'd rather they focused on writing a good and descriptive commit message and if it's formatted correctly, that's a bonus.<\/p>\n\n<p>Whilst I could automate checks for this, I don't think it's the best use of everyone's time and, especially for Junior Developers who already have enough to learn already, not where their focus should be.<\/p>\n\n ",
"processed": "\n <p><a href=\"http:\/\/default\/daily\/2024\/05\/17\/why-i-dont-commit-with--m\">Yesterday<\/a>, I mentioned the 50\/72 rule when writing Git commit messages.<\/p>\n\n<p>The first line in the commit message is the subject line and should be no longer than 50 characters.<\/p>\n\n<p>Any additional lines are the message body and should be wrapped at 72 characters.<\/p>\n\n<p>As I said, I have Neovim configured to format my commit messages based on these rules, although they're more like guidelines.<\/p>\n\n<p>There's no hard limit on the number of characters in the subject line or the number of characters in the body.<\/p>\n\n<p>The commit will work and not be rejected when pushing to your remote repository.<\/p>\n\n<p>There are likely post-commit <a href=\"http:\/\/default\/daily\/2022\/08\/16\/what-are-git-hooks-why-are-they-useful\">Git hooks<\/a> to do this, but by default, things will work.<\/p>\n\n<p>A commit message to Drupal core today was 178 characters long, including the issue ID and contributors.<\/p>\n\n<p>When working on project teams, ideally, everyone would follow the 50\/72 rule, but if they don't consistently, I don't think it's an issue.<\/p>\n\n<p>I'd rather they focused on writing a good and descriptive commit message and if it's formatted correctly, that's a bonus.<\/p>\n\n<p>Whilst I could automate checks for this, I don't think it's the best use of everyone's time and, especially for Junior Developers who already have enough to learn already, not where their focus should be.<\/p>\n\n ",
"summary": null
}
],
"feeds_item": [
{
"imported": "1970-01-01T00:33:45+00:00",
"imported": "1970-01-01T00:32:50+00:00",
"guid": null,
"hash": "9217d539c0fc267a1534cb9e166f41ee",
"target_type": "feeds_feed",