microsoft / microsoft/component-detection
Publish as a .NET tool?
Open
Nobody has claimed this yet.
.NET
status:requirements
type:feature
version:minor
- Dominant language
- C#
- Stars
- 553
- Forks
- 135
- Avg merge
- 20h 58m
- Merged PRs (30d)
- 6
Description
I would like to manage the component-detection configuration for my repository from my local tools configuration file.
AB#2123785
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
No files, tests, or entry points are named. Start by clarifying whether the request is to publish component-detection as a .NET tool, to read configuration from a local tools configuration file, or both. Done should be defined against the clarified request, including how repository configuration is managed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100