-
Notifications
You must be signed in to change notification settings - Fork 0
Revert to .sln format for CI/CD compatibility #13
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| ### 2026-02-20: Revert to .sln format for CI compatibility | ||
|
|
||
| **By:** mpaulosky (via Copilot) | ||
|
|
||
| **What:** CI/CD pipeline failing with .slnx format. Reverting all processes to use legacy .sln solution format. GitHub Actions workflows and build commands must reference .sln instead of .slnx. | ||
|
|
||
| **Why:** The squad-ci.yml build step is failing because `dotnet restore` and `dotnet build` do not properly support the modern .slnx format in the CI environment. GitHub Actions on ubuntu-latest cannot parse .slnx files correctly. Reverting to .sln ensures compatibility with existing CI infrastructure. |
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
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
| Original file line number | Diff line number | Diff line change | ||
|---|---|---|---|---|
| @@ -0,0 +1,79 @@ | ||||
|
|
||||
|
||||
Comment on lines
+2
to
+6
Copilot
AI
Feb 20, 2026
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.
This PR’s goal is to revert processes to the legacy .sln format, but IssueManager.slnx is still present in the repo root. Keeping both formats increases the chance that local scripts/CI steps that omit an explicit solution (e.g., dotnet restore from the repo root) will select the wrong one. Consider removing IssueManager.slnx (or clearly documenting that only IssueManager.sln should be used) to avoid ongoing ambiguity.
This file was deleted.
Oops, something went wrong.
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.
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.
The workflow still runs
dotnet restorewithout specifying a solution/project. Since IssueManager.slnx still exists at the repo root, restore can pick up the .slnx (and fail) depending on how MSBuild resolves the default. Calldotnet restore IssueManager.sln(or pass the same solution used for build) to make the CI behavior deterministic.