Automate build on commit#60
Closed
speige wants to merge 1 commit into
Closed
Conversation
speige
force-pushed
the
GitHubBuildAction
branch
2 times, most recently
from
December 8, 2024 08:57
39e5e9b to
0922baa
Compare
speige
force-pushed
the
GitHubBuildAction
branch
from
September 6, 2025 21:04
0922baa to
f412073
Compare
speige
force-pushed
the
GitHubBuildAction
branch
from
September 6, 2025 21:27
f412073 to
8da020d
Compare
Contributor
Author
|
Closing since you've implemented your own .yml workflows |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 will generate a new zip with binaries any time a commit is made to master, sending email notification to author of build errors, & allowing dependent projects to download an updated build to replace their NuGet version, if they desire a more recent unofficial build.
The git commit SHA is included in the dll's version number, so even if the official version (5.7.1.0) isn't updated, it's still obvious which git commit the dlls were compiled from.
