add automatic GitHub release creation #21
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@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 Seems that worked 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.