Maria Zhelezova

Hey @cegekaJG First of all, thank you for taking the time to contribute to the AL-Go repository. The PR looks okay. However, there's a certain process when using 3rd party...

Hi @gntpet and thank you for your question. Currently, AL-Go and _BCContainerHelper_ do not support running breaking changes validation. It could be an enhancement we can consider for future versions....

Hey @gntpet Using `excludeEnvironments` setting (see doc in [AL-Go settings](https://github.com/microsoft/AL-Go/blob/7b77018959e05b87c751e9b129837c4c2b53600d/Scenarios/settings.md)) will hopefully solve your issue.

@dsaveyn Thank you for reaching out. `fullBuildPattern` is actually exclusively used for pull request builds: changes to any path in the `fullBuildPattern` will trigger a full build. It means that...

No, not really. But we will discuss if it's worth adding such functionality.

Splitting the build and test jobs is possible even today by splitting the apps into different AL-Go projects. Of course, that way apps and test apps will be in different...

As using an internal AL-Go repository isn't a supported scenario today, there isn't anything to address. We'll try to evaluate supporting such cases as part of #853

This is, unfortunately, a known limitation. For now, I can only recommend re-using our script from BCApps: https://github.com/microsoft/BCApps/blob/main/build/scripts/DevEnv/NewDevEnv.ps1 We'll be working on providing something similar through AL-Go for GitHub as...

Hi @louagej Can you please share the full log (in a zip file)?

I see the created container is _filesOnly_, so no wonder there is failure. However, the apps only need to be built when creating an online dev environment. As a mitigation,...