eng: add --no-restore to CI build steps after dotnet restore#200
Merged
shanselman merged 1 commit intoopenclaw:masterfrom Apr 23, 2026
Merged
Conversation
Contributor
Author
|
The patch from issue #195 originally included |
Each dotnet build / dotnet publish step that followed an explicit dotnet restore was redundantly re-checking NuGet dependencies. Adding --no-restore eliminates that I/O on every CI run. Five steps updated: Build Shared Library, Build Tests (x2), Publish WinUI Tray App, Build Command Palette Extension. The WinUI test build (-r win-x64) is excluded: the generic dotnet restore in the test job runs without -r win-x64, so project.assets.json lacks that RID target and --no-restore would fail with NETSDK1047. Closes openclaw#195. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
AlexAlves87
force-pushed
the
repo-assist/eng-ci-no-restore-2026-04-22
branch
from
b499cb7 to
d1d1e7e
Compare
13 tasks
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
2 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.
Each
dotnet build/dotnet publishstep in thetest,build, andbuild-extensionjobs was redundantly re-checking NuGet dependencies even thoughdotnet restorehad already run as an explicit prior step. Adding--no-restoreeliminates that overhead.Five commands updated:
testjob: Build Shared Library, Build Tests (both projects)buildjob: Publish WinUI Tray Appbuild-extensionjob: Build Command Palette ExtensionNote: the WinUI test build (
dotnet build src/OpenClaw.Tray.WinUI -c Debug -r win-x64) is excluded — the genericdotnet restorein the test job runs without-r win-x64, so adding--no-restorethere causes NETSDK1047.No source changes. Existing test suite is unaffected.
Closes #195.