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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Add support for GitHub Packages #173
chore: Add support for GitHub Packages #173
Changes from all commits
0a0273d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this because we're not building on Windows in the job? Will this have any impact on the release build (it does run on windows)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep! It gives
dotnet build
enough context to build thenet462
TFM on Linux, so we can run package builds onubuntu-latest
which, among other reasons, runs circles aroundwindows-latest
fordotnet restore
and anything else that uses compression:windows-latest
:ubuntu-latest
:It should have no impact since it's conditioned on the
OS
var and the reference assemblies won't be included in the compilation, leavingdotnet
to find the actual assemblies in the GAC (or on disk, can't remember which it actually checks, so don't quote me on this part).But it does mean, that once everyone is comfortable with it (i.e. this workflow runs without issues a few times), we could then update
release.yml
to run onubuntu-latest
too.That workflow obviously runs less frequently than
ci.yml
, so thedotnet restore
perf won't be as big of a consideration in that case, but I personally feel better building my internal stable releases on theubuntu-latest
runners. Things just always seem to work better there lol (e.g. cli perf, line endings, etc).edit: opened #195 for later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense. I'm in favor of that change in the future. Thanks for the explanation 🙏