100 lines
No EOL
3.4 KiB
JSON
100 lines
No EOL
3.4 KiB
JSON
{
|
|
"uuid": [
|
|
{
|
|
"value": "54cbe9f9-4a89-418d-bf1e-f337025370a9"
|
|
}
|
|
],
|
|
"langcode": [
|
|
{
|
|
"value": "en"
|
|
}
|
|
],
|
|
"type": [
|
|
{
|
|
"target_id": "daily_email",
|
|
"target_type": "node_type",
|
|
"target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7"
|
|
}
|
|
],
|
|
"revision_timestamp": [
|
|
{
|
|
"value": "2025-04-21T01:21:34+00:00"
|
|
}
|
|
],
|
|
"revision_uid": [
|
|
{
|
|
"target_type": "user",
|
|
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
|
}
|
|
],
|
|
"revision_log": [],
|
|
"status": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"uid": [
|
|
{
|
|
"target_type": "user",
|
|
"target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849"
|
|
}
|
|
],
|
|
"title": [
|
|
{
|
|
"value": "Optimise for revertability"
|
|
}
|
|
],
|
|
"created": [
|
|
{
|
|
"value": "2024-05-10T00:00:00+00:00"
|
|
}
|
|
],
|
|
"changed": [
|
|
{
|
|
"value": "2025-04-21T01:21:34+00:00"
|
|
}
|
|
],
|
|
"promote": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"sticky": [
|
|
{
|
|
"value": false
|
|
}
|
|
],
|
|
"default_langcode": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"revision_translation_affected": [
|
|
{
|
|
"value": true
|
|
}
|
|
],
|
|
"path": [
|
|
{
|
|
"alias": "\/daily\/2024\/05\/10\/optimise-for-revertability",
|
|
"langcode": "en"
|
|
}
|
|
],
|
|
"body": [
|
|
{
|
|
"value": "\n <p>There are two things I avoid when merging changes in Git.<\/p>\n\n<p>Merge commits and squashing commits.<\/p>\n\n<p>Both make it hard to revert changes if needed once they've been merged, such as a major bug in production and you quickly need to roll back.<\/p>\n\n<p>Merge commits are difficult to revert and if a commit has been squashed into one larger commit, you can't revert it without also reverting everything else.<\/p>\n\n<p>Working with small, unsquashed commits makes it simple to revert a specific one and only that one.<\/p>\n\n<p>If I need to revert something, I want to be able to do as simply and specifically as possible.<\/p>\n\n<p>Optimise for revertability.<\/p>\n\n ",
|
|
"format": "full_html",
|
|
"processed": "\n <p>There are two things I avoid when merging changes in Git.<\/p>\n\n<p>Merge commits and squashing commits.<\/p>\n\n<p>Both make it hard to revert changes if needed once they've been merged, such as a major bug in production and you quickly need to roll back.<\/p>\n\n<p>Merge commits are difficult to revert and if a commit has been squashed into one larger commit, you can't revert it without also reverting everything else.<\/p>\n\n<p>Working with small, unsquashed commits makes it simple to revert a specific one and only that one.<\/p>\n\n<p>If I need to revert something, I want to be able to do as simply and specifically as possible.<\/p>\n\n<p>Optimise for revertability.<\/p>\n\n ",
|
|
"summary": null
|
|
}
|
|
],
|
|
"feeds_item": [
|
|
{
|
|
"imported": "2025-04-21T01:21:34+00:00",
|
|
"guid": null,
|
|
"hash": "e672c406c3284040f0cc248f0e94010b",
|
|
"target_type": "feeds_feed",
|
|
"target_uuid": "90c85284-7ca8-4074-9178-97ff8384fe76"
|
|
}
|
|
]
|
|
} |