{{ message }}
Add CI build via GitHub Actions#7108
Merged
Merged
Conversation
Contributor
Contributor
mitchelsellers
approved these changes
Mar 13, 2026
donker
approved these changes
Mar 13, 2026
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
4 participants
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.
Summary
This PR enables running CI builds via GitHub Actions.
I had it run against that branch until it worked, and then updated it to only run for
develop,main,release/*, and pull requests (as well as manual dispatch).Differences from Azure DevOps
BuildServerSetVersionCake task, it doesn't seem to have a corollary in GitHub ActionsI wasn't able to test the new
CreateGitHubPullRequestCake target. At the very least, we don't yet have the required secrets defined in GitHub. I assume there's an easier way to do that in GitHub Actions, but maybe it's easier to keep it working this way until we turn off Azure DevOps. /cc @valadasReasoning
We can add on steps or workflows which do trusted publishing of NuGet packages. In general, there should be better integration of annotations from CI build errors.