News for hackers. Stuff that matters.

A comment on Blog with Markdown and Git, and degrade gracefully through time. Parent comment

Re:Blog with Markdown and Git, and degrade gracefully throug... by gglitch on Monday February 08, 2021 @02:51PM (#26069249)
I have a branch and remote called "publish", and a branch and remote called "draft". I suppose if I ever accidentally pushed the draft branch to the publish remote, I'd just delete the branch from the remote.
[ Parent | on HN ]
Re:Blog with Markdown and Git, and degrade gracefully throug... by samatman on Monday February 08, 2021 @05:20PM (#26071022)
You could set up an integration to automatically reject a branch called 'draft', if you really cared to.

Edit: this is easy, in fact: you make a copy of your 'publish' branch on the publishing site, call it 'draft', and then protect it.

[ Parent | on HN ]