Repository navigation
chore(build): migrate to slnx and organize solution folders - #1101
Merged
Merged
Conversation
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
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.
What and why
Replace
Cluckwork.slnwithCluckwork.slnxso the IDE can show the frontend and working documentation alongside the backend. Group the existing 10 projects undersrcandtests; include all 278 frontend source files, supporting assets/scripts, runbooks, schema overview/viewpoints, and security docs. Add the stable build files, repo guides, workflows, deployment files, and Dockerfile proposed in #1100. Decision records are excluded from the solution tree.Update CI commands, path filters, developer scripts, hooks, current documentation, and repo-root finders. Read the XML project inventory in the CI-matrix guard and update the lockfile inventory check for the new format. A new guard checks that every listed solution item exists, including nested frontend files. File additions, removals, and renames still require maintaining the explicit list.
Remove the unused solution COPY from the Docker restore layer and exclude the solution from both image-cache keys. Restore targets the API project directly, so solution navigation changes no longer invalidate its cache.
Closes #1100
How it was verified
src/Cluckwork.Api/Dockerfile.dotnet sln Cluckwork.slnx listpassed.git diff --checkpassed.GitHub CI, including the E2E smoke workflow, will validate the pushed commit.