Комментарии:
Oh also, if anyone runs across that the version thing used in here no longer works, this is what i ended up using:
- name: version-from-tag-action
id: version
uses: Im-Fran/[email protected]
with:
remove-first-character: 'v'
version-variable-name: 'VERSION'
- name: 'Pack Project'
run: dotnet pack ${{ env.PROJECT_PATH }} --no-restore --no-build --configuration Release --include-symbols -p:SymbolPackageFormat=snupkg -p:PackageVersion=${{ env.VERSION }} --output ${{ env.PACKAGE_OUTPUT_DIRECTORY }}
Thanks man, a real life saver for an actions newb like me :P
ОтветитьYou explanation is amazing!
ОтветитьThanks for the explanation.
I've tried and noticed that this argument need to be addedbto the pack cmd :
" -p:SymbolPackageFormat=snupkg"
to use the '.snupkg' extension for the symbols instead of 'symbols.nupkg'. Otherwise, the push tries to push the symbolic file as well
You are awesome !
Ответитьhow I can fix it ? error: Could not find a part of the path in section Push package
Ответитьexcellent Sean. saved me a few hours of research - mucho thanko
ОтветитьThank you man, much help!
ОтветитьThank you. This will not se the version of the assembly, will it? Any automation about that?
ОтветитьI fucking love you man!
ОтветитьThis was very useful.
ОтветитьThanks for this great tutorial, Can we use GitHub actions to deploy packages to Azure Artifacts? If yes what are the modifications to your code to do that?
ОтветитьPerfect, exactly what I needed.
ОтветитьThank you it's a great tutorial!
ОтветитьWill this give me a Nuspec file with Dependencies because the nuget pack quietly leaves those out of the file... i just sadly found out.
ОтветитьHow to deploy wpf application to exe
Ответить