"deliverToAppsource" usage for multi-project (multiple apps per project) repo?

[SteveKrisjanovsD365]

We currently have an appsource repo structured as follows:

• Repo: http://github.com/org/reponame
  • "W1" project
    • "W1 App 1"
    • "W1 App 2"
  • "CA" project
    • "CA App 1"
    • "CA App 2"

currently we are manually codesigning and publishing our appsource app revisions outside al-go for github

If I'm reading https://github.com/microsoft/AL-Go/blob/main/Scenarios/PublishToAppSource.md correctly, it appears that each project only supports one "deliverToAppsource" structure per project (and the "deliverToApprouce" only defines one main app / offer per deliverToAppsource). how can we leverage deliverToAppsource for scenarios where there are MORE than one app per project?

[freddydk]

Every project is one AppSource app, but can have multiple library apps, which will be pulled along.
You should not put multiple W1 apps in the same repository/project.

The guidelines are:

1. repository are a series of apps, which are released together.
2. projects are a series of apps, which are installed together.

If you have two standalone appsource apps - they are not released together and should be in different repositories or at least different project.