Description
Currently, a module is only published if git detects code changes for a module when comparing with Head^-1.
This can lead to some undesired behavior if you set up CARML for the first time, directly in main, and run the pipelines without any module changes. If that's the case, you won't be able to publish unless you apply a workaround such as a modification of the version.json file.
To mitigate this behavior we could add some logic to the publishing to the dedicated target locations (i.e., ACR, Template Specs, Universal Packages) that not only checks for changes, but also if there is already a version in that target location. If there is none, the pipeline could then decide to publish even if there are no module changes.
Description
Currently, a module is only published if git detects code changes for a module when comparing with Head^-1.
This can lead to some undesired behavior if you set up CARML for the first time, directly in main, and run the pipelines without any module changes. If that's the case, you won't be able to publish unless you apply a workaround such as a modification of the
version.jsonfile.To mitigate this behavior we could add some logic to the publishing to the dedicated target locations (i.e., ACR, Template Specs, Universal Packages) that not only checks for changes, but also if there is already a version in that target location. If there is none, the pipeline could then decide to publish even if there are no module changes.