Skip to content

Commit 09f1e32

Browse files
committed
Publish the NuGet package also on GitHub
Now that I tested the GitHub Package Registry there's version 1.0.0-alpha.0.97 which can not be deleted and is displayed on the main page of the repository. I can see how this could cause confusion if it stays at an alpha version while the final version is published on nuget.org. So I'll publish releases on GitHub too in order to have the package display a final version on the GitHub project page. Nobody will use it since it requires adding a custom NuGet feed and requires authentication but at least it will generate confusion about what is the currently published version.
1 parent d9d4b9d commit 09f1e32

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

.github/workflows/continuous-integration.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ jobs:
3838
runs-on: macos-latest
3939
needs: package
4040
if: github.ref == 'refs/heads/prerelease' || startsWith(github.ref, 'refs/tags')
41-
name: Publish package on nuget.org
41+
name: Publish NuGet package
4242
steps:
4343
- name: Create tag
4444
if: github.ref == 'refs/heads/prerelease'
@@ -50,3 +50,5 @@ jobs:
5050
with:
5151
name: nuget-package
5252
- run: dotnet nuget push ${{ needs.package.outputs.nupkg-filename }} --source https://api.nuget.org/v3/index.json --api-key "${{ secrets.NUGET_API_KEY }}"
53+
- run: dotnet nuget add source https://nuget.pkg.github.com/${{ github.repository_owner }}/index.json --name github --username ${{ github.repository_owner }} --password ${{ github.token }} --store-password-in-clear-text
54+
- run: dotnet nuget push ${{ needs.package.outputs.nupkg-filename }} --source github

0 commit comments

Comments
 (0)