Skip to content
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

WI00764279 - NCN Diagrams - Move WTG.Blazor.Diagrams to nuget.org - Documentation #46

Prev Previous commit
Next Next commit
added that it can be run manually
vinnie-fialok committed Jul 15, 2024
commit 82d31539382bde4ec5822432ce4adf909de6560a
2 changes: 1 addition & 1 deletion WTGPublishPackageGuide.md

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's not add this doc to the repo. It seems very specific to WTG.
Happy to approve the PR only removing the PushNuget.ps1 script.

Original file line number Diff line number Diff line change
@@ -5,7 +5,7 @@ This doc explains how the package we use at WTG is updated.
## Creating Releases with Github Actions

### Releases
When a PR is **merged to master**, the GitHub Action 'Create release' should run. This action creates a GitHub Release and uploads the package to the release. The package created should contain Blazor.Diagrams.dll, Blazor.Diagrams.Core.dll and SvgPathProperties.dll.
When a PR is **merged to master**, the GitHub Action 'Create release' should run. It can also be run manually if needed. This action creates a GitHub Release and uploads the package to the release. The package created should contain Blazor.Diagrams.dll, Blazor.Diagrams.Core.dll and SvgPathProperties.dll.

This action also pushes this release to NuGet, see [WTG.Z.Blazor.Diagrams on nuget](https://proget.wtg.zone/feeds/Gallery/WTG.Z.Blazor.Diagrams/versions). We access this internally at WiseTech through ProGet, see [WTG.Z.Blazor.Diagrams on proget](https://proget.wtg.zone/feeds/Gallery/WTG.Z.Blazor.Diagrams/versions). See [this article](https://inedo.com/proget/private-nuget-server) for more info about how and why proget is used as a source for NuGet rather than accessing NuGet directly.

Loading