Skip to content

Update Library.Template #1659

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.

Sign up for GitHub

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

Open
Andrew Arnott (AArnott) wants to merge 3 commits into
base: main
Choose a base branch
from
+1 −15
Open

Update Library.Template #1659

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f1c1a2d
Drop GitHub Actions section
AArnott Aug 24, 2026
511e4ab
Reapply "Update dependency dotnet-coverage to v18.10.0 (552)"
AArnott Aug 25, 2026
bb35c1f
Merge the microbuild branch from https://github.com/aarnott/Library.T…
invalid-email-address Aug 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .config/dotnet-tools.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
"rollForward": false
},
"dotnet-coverage": {
"version": "18.9.0",
"version": "18.10.0",
"commands": [
"dotnet-coverage"
],
Expand Down
14 changes: 0 additions & 14 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,20 +52,6 @@ Use `nbgv tag` to create a tag for a particular commit that you mean to release.

Push the tag.

### GitHub Actions

When your repo is hosted by GitHub and you are using GitHub Actions, you should create a GitHub Release using the standard GitHub UI.
Having previously used `nbgv tag` and pushing the tag will help you identify the precise commit and name to use for this release.

After publishing the release, the `.github/workflows/release.yml` workflow will be automatically triggered, which will:

1. Find the most recent `.github/workflows/build.yml` GitHub workflow run of the tagged release.
1. Upload the `deployables-Linux` artifact from that workflow run to your GitHub Release.
1. Any nuget packages in the `deployables-Linux` artifact will be pushed to nuget.org.

The workflow is written to leverage NuGet.org Trusted Publishing.
You should set `NUGET_USER` as a repo secret to satisfy Trusted Publishing requirements.

### Azure Pipelines

When your repo builds with Azure Pipelines, use the `azure-pipelines/release.yml` pipeline.
Expand Down
Loading