[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"sanity-dIJk5WCSoHcc6Zsmklf69PcGgUlW0wBZ2qFUy7G7O8I":3},{"data":4,"sourceMap":-1},{"info":5,"latest":14,"pinned":54},{"_createdAt":6,"_id":7,"_rev":8,"_type":9,"_updatedAt":6,"descriptionText":10,"slug":11,"title":13},"2023-05-23T16:43:21Z","wp-tagcat-source-control","9HpbCsT2tq0xwozQfkc4ih","blogTag",null,{"current":12},"source-control","source control",[15],{"_id":16,"author":17,"commentCount":28,"comments":29,"excerpt":30,"featureTag":10,"image":31,"publishedAt":34,"slug":35,"sponsored":10,"tags":37,"title":53},"wp-post-17746",[18],{"_id":19,"avatar":20,"name":25,"role":10,"slug":26},"wp-author-cap-17749",{"_type":21,"asset":22},"image",{"_ref":23,"_type":24},"image-7006b3fbc1df1efae3628b1394868bde13ef3c35-48x48-jpg","reference","Tobias Günther",{"current":27},"tgunther",20,true,"Git branches allow you to keep different versions of your code cleanly separated. Here's a look at how they work and why you should know about them.",{"_type":21,"asset":32},{"_ref":33,"_type":24},"image-98a949559eab7bccbe1792edf4600470af293d2f-1200x630-jpg","2021-04-05T14:00:00.000Z",{"current":36},"a-look-under-the-hood-how-branches-work-in-git",[38,42,47,51],{"_createdAt":6,"_id":39,"_rev":8,"_type":9,"_updatedAt":6,"slug":40,"title":41},"wp-tagcat-branches",{"current":41},"branches",{"_createdAt":6,"_id":43,"_rev":8,"_type":9,"_updatedAt":6,"slug":44,"title":46},"wp-tagcat-code-for-a-living",{"current":45},"code-for-a-living","Code for a Living",{"_createdAt":6,"_id":48,"_rev":8,"_type":9,"_updatedAt":6,"slug":49,"title":50},"wp-tagcat-git",{"current":50},"git",{"_createdAt":6,"_id":7,"_rev":8,"_type":9,"_updatedAt":6,"slug":52,"title":13},{"current":12},"A look under the hood: how branches work in Git",[]]