Because the Mac app for Micro.blog is open source and we’re holding off announcing some new stuff until next month, I can’t just push in-progress changes to GitHub. Kind of makes me nervous having this code only on my Mac. (I do have backups but just daily.)

@manton Maybe we can create another "remote" to push to... and then try not to push to the public one 🤣

@manton Just create a private GitHub repo, add it as a second remote (e.g. instead of 'origin’, name it ‘private’) and push to there?

@manton probably lots of smarter folks are suggesting different approaches, but a simple one would be to work on a fork and then when ready to launch, merge with the official repo.

@uliwitness @tkoola I probably should create a private repo... It seems like extra clutter but sure would be nice to have another copy.

@manton Why not push it to a private repo somewhere?

@manton You probably know this, but you can push to a different repo in this meantime…

@manton I see that you are getting a lot of posts about code management. Reminds me of this one time someone was keeping different folders of code. One of my friends mocked her, but the joke was on him because she shipped and he didn’t. Best of luck with whatever solution you use.

@manton Host your own git server on a RaspberryPi. Easy if you know a bit of Linux command line. Then you could back it up to your own git server

@manton just saying, some of us are flexible about things that don’t work and can keep a secret…

@jsonbecker @manton Agree with Jason. We won't write about anything, Manton. And we complain either 🤐

@jsonbecker @amit I try to be pretty transparent about working on new things but this one is gonna stay under wraps. Probably. 🙂

@manton @jsonbecker @amit You oughta know by now how persistent a group we are here. We convince each other to cave on purchases all the time. What makes you think you’re immune to us making you cave on this, and spilling the proverbial beans? 😉

@pimoore 🤣 🤣

@manton If you get in touch with me, I could prepare a YouTube video that presents the new feature and could come out at the same time you release the new feature! Think about it how this could be impactful! 😉

@pimoore @manton Absolutely, what Pete says 😉 ...spill the beans... 😵‍💫

@manton why not add another remote repository that’s private or have a private fork which you eventually merge back? (Genuine question)

@friend I did end up doing that. Resisted it at first just to keep things simple.