What’s best practice with #git for a personal site that I’m developing while live but also publishing posts for? I’m using a single dev branch for the initial building but for writing posts on the fly? A new branch for each post, PR, then merge? #WebDev
@karenfriesen whatever is the least amount of work. For me I've just gone with a single branch and I've set up a workflow for posts where I mark them as draft and they won't get published (unless env=development)
@gustav a good rule of thumb 😄 I’m trying to make the posting process as frictionless as possible so the new branch option might be easiest way to just get my random thoughts up there from my phone
@karenfriesen Everyone's process is different. I just couldn't be arsed with multiple branches especially since I usually have drafts sitting for a long time before publish. It would be loads of branches.