Closed FH-Inway closed 6 months ago
@Splaxi I'm not 100% sure that the transfer of the ApiKey secret works. As far as possible, I tested it on my fork. If it doesn't work, please restore the previous version of build.yml. I will then take a look at setting up an end to end test on my fork.
@Splaxi Note that the input to skip the creation of the GitHub release in the manually triggered action does not work, the release will always be created.
@Splaxi I'm not 100% sure that the transfer of the ApiKey secret works. As far as possible, I tested it on my fork. If it doesn't work, please restore the previous version of build.yml. I will then take a look at setting up an end to end test on my fork.
@Splaxi Seems that worked 😄 Next step see https://github.com/d365collaborative/d365fo.tools/discussions/813.
This extends the build GitHub action by adding a step to automatically create a GitHub release.
As preparation of consolidating all actions shared by the d365collaborative repositories, the actual build steps were moved into a reusable workflow.
To demonstrate the reusable workflow, a new build action was added that can be triggered manually and allows disabling the release creation on both PowerShell gallery and GitHub. This is mainly intended for testing the reusable workflow.