microsoft / microsoft/component-detection
Switch to `dotnet-releaser`
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 553
- Forks
- 135
- Avg merge
- 20h 58m
- Merged PRs (30d)
- 6
Description
Currently we build and package using our own build scripts. However dotnet-releaser appears to be a much more comprehensive and easier way to build, package, and release.
It will allow us to more easily build across a wide range of operating systems and packaging methods.
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 locating the project's own build and packaging scripts, then compare their current responsibilities with dotnet-releaser's documented build, package, and release capabilities. Done means the existing scripts are replaced or integrated so the project can build across the intended operating systems and packaging methods, with release behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, release
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100