Subj : Re: Talisman Git Repo
To   : apam
From : tenser
Date : Tue Feb 02 2021 02:54:00

On 01 Feb 2021 at 01:34p, apam pondered and said...
 
 ap> The reason I didn't to begin with was so people were always on the same
 ap> version, which would be easier to debug (and I often commit broken
 ap> things), so perhaps instead we could say.. if you want an expectation of
 ap> a working system use a release, if you don't mind hiccups, you can use
 ap> git.

I think that's a great idea.

In case it might help, a workflow that I've settled on that I
really think works well is to try and keep the main branch clean,
but have a "wip" branch that I put all my intermediate commits
into.  When I think that I'm happy with how things look, I just
squash-merge it into main.  That way, I can make as many little
"checkpoint" commits as I want in various states of brokenness,
but main is always buildable with the latest "released" code.

I think I first saw something similar described here:
https://sandofsky.com/workflow/git-workflow/

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.