solarwinds / solarwinds/net-changesets
Upon release, create a GitHub release and also publish the NuGet package to GitHub Packages
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 14
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
We are currently creating GitHub releases manually, which is a tedious and repetitive task.
We can use the generated changelog by the changeset tool. Also, use features from GitHub-generated changelogs, like New Contributors, and include contributors. Also include a badge in the NuGet org-released version.
Example of manually created release: https://github.com/solarwinds/net-changesets/releases/tag/0.1.2
Push NuGet also to GitHub Packages as an alternative to NuGet.org.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing release process and the changeset tool's generated changelog, using the manually created 0.1.2 release as the reference. Define the release output as a GitHub release with changelog and contributor information, plus publication of the NuGet package to GitHub Packages with the requested badge and NuGet.org release remaining available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100