Based on the documentation the version information of a package will be overwritten when GitHub workflows are used (see link and screenshot below). To me it is not completely clear how this works. Is it the reusable workflow that does this or the ‘dotnet publish’ step that you can use in a workflow? In addition, what content will be used to overwrite the version comment?
Hi Michiel
This is indeed not fully clear in the documentation.
This will only be overwritten when using the reusable workflows that Skyline provides. If you create your own workflow and do the ‘dotnet publish’ yourself, then you can also set the VersionComment via the command like regular MSBuild properties:
– name: Publish Release
env:
DATAMINER_TOKEN: ${{ secrets.DATAMINER_TOKEN }}
shell: pwsh
run: |
dotnet publish `
-p:Version=”${{ github.ref_name }}” `
-p:VersionComment=”CUSTOM COMMENT” `
-p:CatalogPublishKeyName=”DATAMINER_TOKEN” `
-p:CatalogDefaultDownloadKeyName=”DATAMINER_TOKEN” `
-c Release `
Regarding the content when it’s done via the reusable workflows:
- If the release was made via creating a tag (without using the GitHub Releases):
- It will try to fallback and use the git commit message or the tag value.
- If the release was made via creating the release on the UI of GitHub (and creating the tag at the same time), then the description of that release will be used.
- This also allows to use markdown to have more flexibility in how you want to format the text.