Make it difficult (or impossible) to mess up the master branch

Feature Requests
21

I see this marked as Beta now. Can I test it somehow?

22

Presuming that “this” means “the Anvil IDE”, I’d start here: Anvil Docs | New Editor

23

The thread was originally marked as “[Beta]” because years ago when it was first created, the new editor was a beta creature! It’s now all grown up, and is no longer “new” - it’s just the Anvil Editor - so to avoid confusion I’ve removed the beta tag from this thread.

4 Likes
24

I checked my GitHub account today for the first time in ages, and now it’s kindly suggesting I protect the master branch:

image
image855×77 7.25 KB

Until a few years ago, Anvil had a simple and safe setup:

  • a readonly published branch
  • a read/write master branch for development

Then things changed — probably not because of GitHub, but let’s blame it anyway:

  • published became read/write (less safe)
  • it was renamed to master, creating confusion for existing apps where master was already used for development

That’s when I started this thread, asking to reverse those two changes:

  • Make published read-only again — the old workflow was working just fine
  • Rename master back to what it was, or drop the name entirely — reusing it for something else just added unnecessary inconsistency

And now GitHub seems to agree: maybe the default branch (sorry, “main”, not “master”) really should be read-only.

You’re welcome, GitHub. Happy to lead the way.
:smile:

2 Likes