For a CI/CD pipline. I have read your posted documentation and code. I'm curious how github would handle two staging environments and your meta files for dashboards and LDM? If two users were working off two different clones of the reporting base and merge them at the same time. Does Github manage to handle the conflicts so that one set of changes doesn't cancel out the others? Also, how have people done a check that during a merge that the metadata is in the correct order/format so that the visuals load correctly?

Hi Doug, thanks for your interest in analytics as code and CI/CD. In general, Github counts with possible merge conflicts and provides ways how to resolve them - there is a good description in their docs: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts Multiple environments e.g. Dev>Staging>Production or similar should not be problem, however, a corresponding pipeline must be developed and configured. Validation which is part of GoodData CLI can provide a level of validation. We have an example here with some more information: https://www.gooddata.com/blog/how-to-create-your-next-analytical-project-in-code/ Please let me know if you have any further questions.

Thanks, I'll take a read