Radzen + Git team workflow?

Hello. I've been assigned a project on my company with RadZen, but we're a team of two people, so using git to keep us both up to date is a necessity. But how does radzen work with git? Is it as simple as using it on any other sort of project? We're used to creating a branch for a new feature, committing to that branch and merging it to the rest of the project when it's all done, but not sure if radzen supports that

Hi @dbranco,

We use exactly git workflow to develop both Radzen itself and all example applications:

Usually you can keep only meta folder in git however if you have custom code you will need client and server folders as well.

Best Regards,

Thank you for the reply @enchev.
So if I do any database connections, new pages, etc, will I need only the meta folder? Can I work on Page A with tables 1, 2 and 3, while my colleague is on Page B with tables 4, 5 and 6, and there won't be any problems while merging?

Database connection is described in .env file and excluded by default:

All files in meta folder are plain JSON and even if you work on same pages you will be able to merge normally.