4 ms·

I used to have my blog source on GitHub, but then it turned out I didn't want my half-finished works-in-progress public. To use a private repository would rathe

I used to have my blog source on GitHub, but then it turned out I didn't want my half-finished works-in-progress public. To use a private repository would rather defeat the point; using a private repo and a public fork is inviting confusion. Now I just use a private repo on my own server, cloned to my dev machine. Does anyone have a usable solution for that problem?

wereHamster 6y ago
Stop caring about unfinished, public wip. In the end, nobody but you is really bothered by its imperfections.
- Smaug123 6y ago
  I knew someone would say that. It's not about imperfections per se; more that I sometimes write stuff that I then reconsider and delete before it ever sees print. Admittedly nowadays I mostly self-censor that stuff before even starting to write it, but a few years ago I wrote a lot more stuff that, after reflection, I considered it would be unwise to go ahead and publish.
simpixelated 6y ago
I personally don't move anything into git until it's close to ready. WIP writing is kept on Bear (Markdown editor). But there are tons of other apps, including ones that sync to a cloud.
gglitch 6y ago
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.
- samatman 6y ago
  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.
approxim8ion 6y ago
I only keep the output on github. So the generator folder with my drafts, posts etc is on my local machine, and whatever output it generates is in its own folder that is a git repo.
vbernat 6y ago
I put my drafts in branches and only push the main branch to GitHub.
- teryyy 6y ago
  going to start doing this!
codazoda 6y ago
I've been thinking about this a lot. I created Ponder so that I could quickly create drafts in my browser. Then I planned to move them to my blog (Markdown on GitHub) when I'm done. I need more than 10 drafts (the current limit in Ponder), but I feel like I'm getting close to a solution that works better for me. I also want to be able to edit across machines (Mac, Chromebook, Phone), so I need to make the app work online. Anyway... https://ponder.joeldare.com https://ponder.joeldare.com
darekkay 6y ago
Using git submodules might work, but it's not very convinient in my experience. I'm now thinking about having a GitHub Action in my private repo that pushes all public posts into a separate public repository automatically

wereHamster 6y ago

Stop caring about unfinished, public wip. In the end, nobody but you is really bothered by its imperfections.

Smaug123 6y ago
I knew someone would say that. It's not about imperfections per se; more that I sometimes write stuff that I then reconsider and delete before it ever sees print. Admittedly nowadays I mostly self-censor that stuff before even starting to write it, but a few years ago I wrote a lot more stuff that, after reflection, I considered it would be unwise to go ahead and publish.

simpixelated 6y ago

I personally don't move anything into git until it's close to ready. WIP writing is kept on Bear (Markdown editor). But there are tons of other apps, including ones that sync to a cloud.

gglitch 6y ago

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.

samatman 6y ago
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.

approxim8ion 6y ago

I only keep the output on github. So the generator folder with my drafts, posts etc is on my local machine, and whatever output it generates is in its own folder that is a git repo.

vbernat 6y ago

I put my drafts in branches and only push the main branch to GitHub.

teryyy 6y ago
going to start doing this!

codazoda 6y ago

I've been thinking about this a lot. I created Ponder so that I could quickly create drafts in my browser. Then I planned to move them to my blog (Markdown on GitHub) when I'm done. I need more than 10 drafts (the current limit in Ponder), but I feel like I'm getting close to a solution that works better for me. I also want to be able to edit across machines (Mac, Chromebook, Phone), so I need to make the app work online. Anyway... https://ponder.joeldare.com https://ponder.joeldare.com

darekkay 6y ago

Using git submodules might work, but it's not very convinient in my experience. I'm now thinking about having a GitHub Action in my private repo that pushes all public posts into a separate public repository automatically