This repository has been archived by the owner on Jul 12, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 125
Better support for monorepo #1088
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
… |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I’d like to keep this issue open. |
Concur |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
🚀 Feature Requests
Currently the
nukeeper repo
command assumes that the repository contains a single solution and works from theNuGet.config
file in the repository root (if it exists). However this assumed 1:1 mapping of repository and solution is incorrect. Many of the repositories I'm working on contain multiple solutions, or the solution is not placed in the repository's root. As a result we cannot use NuKeeper, as it misses our NuGet.config file.Example file layout that I expect to work with NuKeeper:
The text was updated successfully, but these errors were encountered: