We are evaluating Backendless and we are a startup with some developers and some product designers (not UI designers nor programmers).
The non-coders had the idea to use Backendless and I am taking a look and I am curious how the usual team based development cyles would happen:
- forks/branches, merges/conflict management/rebasing
- database/schema migrations
- data migrations
I’ve also taken a look at https://www.youtube.com/@Backendless/videos and used google to search for backendless fork/branch/merge/sync keywords and got no hits.
The only developer/team things I found are about privileges and who can do what on what (roles/acl), correct?
How can I fork a project, make some changes and play those changes back into the main project?