morelinq/MoreLINQ

Add ReSharper's InspectCode to CI builds

Open

#370 opened on Jan 25, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (3,495 stars) (406 forks)batch import
Component-Scriptshelp wanted

Description

Add ReSharper's InspectCode to CI builds for the following benefits:

  • Not require contributors/maintainers to have a ReSharper license
  • Maintainer does not have to highlight basic issues & opportunities
  • A contributor can review basic issues & opportunities without waiting for maintainer
  • Automation of static analysis

Ideally a summary of the code inspection results is published to the PR as a comment with a link to the full report. What would be awesome/nice-to-have is a delta from a previous report on the same PR.

Contributor guide

Tech stack
csharpgithub actions
Domain
ci cdtooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
CI/CD experienceC# basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
First, check the repository's .github/workflows directory for existing CI configuration. Then, research the JetBrains InspectCode CLI tool and how to invoke it in a GitHub Actions workflow. Finally, explore how to generate and post a summary comment on PRs using GitHub actions or scripts.