GitLab Workflow, Branching, and CI/CD for Creatio

Hi everyone,

I’m new to Git-based development with Creatio, and I really need help understanding how a team should properly work using GitLab. We want to avoid mistakes and set up a stable workflow from the beginning.

Could you please help clarify the following topics:

Team development workflow in GitLab
• Should all custom packages be stored in a single repository?

CI/CD - do we need it and how to start?
• Should CI/CD automatically compile and deliver packages after a merge?
• How to deploy changes between Dev → Test → Prod environments correctly?
• What is the minimal recommended pipeline?

Version control content and rules
• What exactly should and shouldn’t be stored in Git? (especially DLLs, Autogenerated folders, bin/obj)

Known limitations or pitfalls
• Which development scenarios are not recommended when working with Git?
• Common conflicts with Creatio database, schema movement, or deleted objects?

I’m completely new to Git and GitLab development with Creatio. I honestly don’t understand how the process should work in a team, so I really need very basic explanations.
Any examples or documentation links, branching strategies, .gitignore examples, or CI/CD templates would help us tremendously.

Thank you very much in advance!