Skip to content

Add root Meraki.Cli.slnx so CI build and CodeQL succeed - #3

Merged
davidnmbond merged 1 commit into
mainfrom
fix/root-solution
Oct 4, 2026
Merged

davidnmbond merged 1 commit into
mainfrom
fix/root-solution

Conversation

@davidnmbond

Copy link
Copy Markdown
Contributor

Problem

CI build fails at Restore with MSB1003: Specify a project or solution file, and CodeQL autobuild fails likewise: the repo root has no solution/project. The only project is content/Meraki.Cli.csproj (the dotnet new template source).

Change

  • Add root Meraki.Cli.slnx (solution items folder + content/Meraki.Cli.csproj), matching peer repos.
  • Add three missing XML doc comments in content/Application.cs and content/Program.cs; the root Directory.Build.props (TreatWarningsAsErrors + GenerateDocumentationFile) now applies to the template and made them CS1573/CS1591 errors.

Verified locally

dotnet restore and dotnet build -c Release --no-restore from the root succeed, 0 warnings, 0 errors. No test projects exist.

Note (not changed here)

dotnet pack is a silent no-op: the Worker SDK project is not packable and Meraki.Cli.nuspec lists no files, so no template .nupkg is produced and the publish job would have nothing to push. Needs a separate fix.

🤖 Generated with Claude Code

…d find the project

The only project lives in content/ (the dotnet new template source), so
`dotnet restore` at the repo root failed with MSB1003. Add a root solution
referencing content/Meraki.Cli.csproj. Building it under the root
Directory.Build.props (TreatWarningsAsErrors + GenerateDocumentationFile)
exposed three missing XML doc warnings in the template source; document them.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity 0
Duplication 0

View in Codacy

AI Reviewer: run a review on demand. To trigger the first review automatically, go to your organization or repository integration settings. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

@davidnmbond
davidnmbond merged commit cf31db2 into main Oct 4, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants