Developer Workflow proposed.

[dougransom]

for DT projects to consider adopting, but at least for natlinkcore:

• main/master renamed to dev, default branch.
• merges from forks/other branches/PRs are squash-merged to dev. Nobody works on the dev branch in DT.
• wheels automatically built with flit but not published to pypi. we can install them from github or something.
• releases are in a release branch. these are squash-merged from the dev branch, with a goal of one commit-release.
• release and dev branches are tagged through a known scheme.
  Motivation: git history very cluttered on main branches where it doesn't need to be. Feature branches in dev forks are where the detailed history can/should be maintained.

bug fix branches — deal with that if we ever actually need one.

[LexiconCode]

Having a clean git history is super important. The issue of doing it one commit per release is it changes how the get history is generated. See https://github.com/dictation-toolbox/natlink/releases/tag/NATLINK_5_3_4