microsoft / microsoft/win-net-test
The win-net-test release process needs to be automated
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 35
- Forks
- 10
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 4
Description
Publishing win-net-test nuget package when a new release is created should be automated, as well as much of the release process as reasonably possible.
Contributor guide
No contributing guide indexed for this repository
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 mapping the existing win-net-test release process and how the NuGet package is currently published. Define which steps should run when a new release is created, then verify that the automated process publishes the package and covers the agreed release steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100