Git Version Control and publishing - Best Practices with Wappler

Hi.
I recently added Git to my project for version control. So far, I have used Visual Studio and VSCode for version control and their UI has worked well for me. I use VSTS (now Azure DevOps) for Git control.
I do not understand completely how Git works, and have just used it for versioning. I have not created any branches or forks.

In Wappler, since there is no UI for this, I used the terminal window to initialize a local Git repository and then used the add remote origin and push commands provided by Azure to upload it. So far, everything has worked.

What I need help with is understanding how well Wappler works with Git. Is there anything I should take care of while using Git? Does creating various branches restrict the working of Wappler in any way? How to select a branch when opening a project? And similar questions… any insights would be helpful.

Also, if anyone can share some resources for dummies to understand how Git works, that would be great too. :slight_smile:

P.S. If I have used some wrong terminology that might cause confusion, please point out. :sweat_smile:

Community Page
Last updated: