Frédéric Vercaemst

> Yes - it is something that needs to be added to AL-Go @freddydk Any update on the above. Devs keep struggling with making local changes and have to wait...

@freddydk I see this is labelled '2024 w1' (although draft PR pending). Can we expect this as part of the April release? Not having to spin up a container for...

I'm not quite sure if I follow the suggested solution, but our goal is to keep to one repository, containing all apps, so we can deploy / release them all...

Maybe provide a similar option 'Run Tests' when manually running the **CI/CD** action 

I'm fully aware that **not** updating these properties / increasing versions would not pose any problems when moving to the next major, as they are indeed just **minimum** versions. However,...

Will there be future AL-GO support for auto-publishing source code documentation using **aldoc.exe** as part of the release action? (Incl. publishing documentation from the private source repo to a public...

Nice work, looks promising 👍

Just did some tests but don't get the expected result: - Workspace with repo with g.xlf / nl-BE.xlf / nl-NL.xlif - Project settings ``` "xliffSync.equivalentLanguagesEnabled": true, "xliffSync.equivalentLanguages": { "nl-BE": "nl-NL"...

@rvanbekkum For the Powershell variant - which we will use for our pipeline - it would be good if the sync commandlets would support an optional parameter to set a...

Thinking on some scenarios: --- **1. Happy flow** (g > nl-BE > nl-NL) **Add label** - Added new label : g.xlif gets a new trans-unit - Sync to nl-BE :...