User Answers

I suggest using local development environment for atelier and using the GitFlow workflow for managing your branches and merges. All the merged code can then be moved, manually or automatically, to your test server and the live server. It works well for us.


We switched to Atelier late last year, mostly to be able to use Git and GitHub. We follow a strict GitFlow workflow. Versioning is working well as long as you follow the workflow.  We release every third week (plus occasional hotfixes) using Jenkins via a test server and a staging server.

We have 7 developers working on the same code base but merge conflicts are very rare and GitHub/Git does a fine job of solving them.

We decided to split them each top level package into separate projects (approx 50) but I'm starting to regret that. I think it is better to have all code in one project and in one repo.

But the F3 does the wrong thing, it goes to the server version of the class, not to the source code.



We are also working on implementing GitHub and Atelier. I have been spending a lot of time researching various options. 

I think you will have to get use to the fact that all code in a repo will always be present, I don't see why this is an issue at all, just use package names to separate them.

Thanks for that. It worked fine but it leads on to the next question. How do get it into my Atelier project automatically?

How do you import the class definition in DataGrip? Can you use the regular class export from Studio?