BrighterCommand / BrighterCommand/Brighter
[Chore] Build Paramore Analyzer
- Dominant language
- C#
- Stars
- 2.5k
- Forks
- 296
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 21
Description
We have added two new projects:
- Paramore.Analyzer
- Paramore.Analyzer.Package
There are Roslyn Analyzers that allow implementers to avoid common problems when setting up Brighter.
We should move these from src/ to tools/
We should ensure that our build: https://github.com/BrighterCommand/Brighter/blob/master/.github/workflows/ci.yml builds the projects in tools
We should ensure that Paramore.Analyzer ships as part of our NuGet packages, using our version numbering etc.
Contributor guide
Research direction
Start with the Paramore.Analyzer and Paramore.Analyzer.Package projects under src/, then inspect .github/workflows/ci.yml to understand the current build entry points. Move both projects to tools/ and verify the workflow builds them. Check the repository's NuGet packaging and versioning configuration so Paramore.Analyzer is included in the published packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github-actions
- Domain
- build-system, ci-cd, release, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100