Replies: 1 comment
-
Hi @66Gramms,
the alternative for version management is to manually update it in the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all!
I'm relatively inexperienced with dotnet but i ran into the issue #103 so I thought I will try and solve it and create a PR. The problem is as someone unexperienced in dotnet I find it hard to build and use the custom built version of this tool.
I've managed to find some steps on MS Docs on how to do this, and this is how far I got before giving up. At this point the built nuget package is in the given folder, i renamed the nupkg and snpukg files to
huskyy
so it's not installed from the internet. When i try installing it with the following commanddotnet tool install --add-source "D:/Repos/FORK/Husky.Net/src/Husky/customHusky" huskyy
I get this error:huskyy is not found in NuGet feeds https://api.nuget.org/v3/index.json, D:\Repos\Husky.Net\src\Husky\bin\Debug\net9.0\Husky, C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\, D:/Repos/FORK/Husky.Net/src/Husky/customHusky.
Can I get some help on how to use a build from source on this, or can someone fix the
Build and usage
section i have in progress ?Build and usage
If you want to contribute you will have to build and use Husky from it's source. To do so follow the steps listed:
./Husky.Net/src/Husky
dotnet build
dotnet pack --output customName
which will generate Nuget package toHusky.net/src/Husky/customName/
. It's important to give a custom name instead of justhusky
as during the install process Nuget will first look at nuget packages from the internet and only after that will it look at our local build.dotnet tool install husky --add-source "Husky.net/src/Husky/customName/"
Beta Was this translation helpful? Give feedback.
All reactions