Anvil's master branch [continued]

Anvil Q&A
6

Ok, so you are suggesting to work with 3 (or more) branches:

  • dev (can be more than one) to develop and debug
  • master to merge all the dev branches into
  • published to link the Published environment to whatever commit you want to pick, typically will be the same as master.

What are the advantages of adding the middleman master?

If we are talking about the published branch being read-and-write, this would only kick the can a little farther. Sooner or later I will inadvertently edit the app while published is checked out and the telephone will start ringing.

I’m not familiar with Guthub workflows, but I have the feeling that this works there because the master branch is (I think) read-only and you may want to publish several versions of a project, the latest as Published and other versions 1.0, 2.0, etc.

I have done only a few contributions to a few Github projects, and I’ve always been forced to create my own branch.

Anvil is not Github. Most apps (all of mine), unlike Anvil Extras, have only one published version. I don’t see the point of having both master and published.

But I would like for Anvil to force me to create (or checkout) a branch before editing.