Features/continuous integration #50
Open
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
Fixed publish path
Updated publish profile path
…oryprimrose/audio-switcher into features/ContinuousIntegration
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.
I've converted the project to the SDK style csproj and added a GitHub Actions yml build script.
To use this you need to enable Actions and point it to
.github/workflows/ci.yml. Any build will produce a zip package against the action. Any build against the master branch or version tag will also create a GitHub release with the package attached.To create a release you need to:
Master branch builds without a tag will be built as Major.Minor.Patch-BetaXXXX. With a tag it will build the package as Major.Minor.Patch. The script will create the GitHub release and publish the compiled (zipped) app to the release only for master or tag builds.
For example, my fork did this for a build. In this case I disabled the branch filter to create a release on the feature branch.
So basically all you have to do is create a tag and push it. Job done :)
One potential issue is that the official GitVersion action does seems to have some issues sometime. See GitTools/actions#76. Current workaround is to just kick the build again.
Closes #44
Closes #48