Hi Anvil team, would it be possible (perhaps under settings) to restrict what’s possible on the master branch? We’re a bunch of developers working on the same application, and whenever we merge into the master branch, the active branch is automatically changed to master. Then we continue developing and forget to change back to our dev branches which risks us breaking the live version.
This has happened a couple of times, and instead of relying on my dev team to remember to switch back to their dev branches, it would be great if we could restrict edits on the master branch.
Also, perhaps the owner of the application can limit who has the ability to merge into master?
It used to be like that, the published branch was read-only and safely out of reach.
Then they changed it, and not only did they remove the ability to make it read-only, they now actually want you to modify it directly.
There are some good workflows out there for both solo developers and teams, but they’re far from intuitive, they require setup, attention, and a bit of reading. The old way didn’t need any of that. It just worked. I’d love to go back to a world where things are intuitive and require no setup, no learning curve, no “workflow guides.” That should be the default.
Even the two workflows @love mentioned are likely used by a tiny percentage of users who happen to be on GitHub. Why should I have to change my way of working just because someone halfway across the world wants to sync with GitHub, when the old behavior was so simple, safe, and setup-free?