this post was submitted on 03 Sep 2026
5 points (85.7% liked)
Writing
1394 readers
2 users here now
Discuss writing, post craft resources, ask for feedback, etc!
No misconduct, including: harassment, abuse, assault, bullying, illegal activity, or discrimination.
Follow all sh.itjust.works rules.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In programming, we use a tool called "Git" to keep track of changes we make to a piece of software, well, and also to collaborate with other devs.
I've been using Git to have a history of how my text-based creative projects evolve (not just writing ๐ ). And then I'm publishing those like an open-source code repository. So, others can go through the history and look at the first draft, or the final edits, or everything in between.
Obviously, though, this does mean that your final result is public as well, unless you find a way to only give access to paying customers, I guess.
To give an example, here's a short tech explainer thingy I wrote: https://trem.codeberg.page/rust/macro_rules.html
And here's the complete change history: https://codeberg.org/trem/pages_src/commits/commit/830718aaa788ac00fb7ba9635c405f7c18cc76fb/src/rust/macro_rules.md
Really useful answer, thank you
You can also do that and keep your git private, maybe available on request for proof.
Yeah I need to get familiar with git for programming so this is great advice, i suppose I'll keep one account private and one public