chore: add GitHub actions and remove Package wapproj #13
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
deansheather
changed the title
|
During the actual publish when we get release CI going, we probably want to make our build matrix manually specify |
spikecurtis
approved these changes
Jan 29, 2025
App/Package.appxmanifest
Outdated
|
|
||
| <Identity | ||
| Name="925b49fc-4648-4967-b4e6-b5473061ee62" | ||
| Publisher="CN=dean" |
There was a problem hiding this comment.
lmfao oops, I guess it defaults to the current user
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.
Adds fmt, test and build jobs using dotnet.
The fmt job currently doesn't match what Rider does, but I think that will be difficult to pull off without using a different formatting tool which I don't want to investigate for now.
Removes the
Packageproject in favor of making theAppproject include the necessary stuff for packaging itself. We weren't getting any benefit from it being in a separate package yet and it was not building correctly in dotnet (only in VS) when they were separated.Closes #7