GitHub Workflows: Automate Code Quality Checks (video)
Learn GitHub Actions workflow structure, PR validation, secrets, caching, and adding lint or static analysis to CI.
Transcript
GitHub Workflows: Automate Code Quality Checks. Here's the short version.
GitHub Actions workflows automate builds, tests, and quality checks on every push or pull request.
Workflow building blocks. Triggers — push, pull_request, schedule, workflow_dispatch. Jobs — parallel or sequential units of work. Steps — shell commands or marketplace actions. Runners — GitHub-hosted or self-hosted.
Pull request validation pattern. Typical PR workflow: checkout → restore dependencies → build → test → optional lint/static scan → upload artifacts. Failed steps mark the check red; branch protection can require checks before merge when admins configure it.
Adding quality checks. Invoke dotnet format, ESLint, or a hosted scanner API after tests. Parse reports to fail on Critical counts.
Want to find these issues in your own code? Connect your GitHub repository to CodeInspector. You'll get findings with the file, line, severity, and a recommended fix, plus HTML and PDF reports for your team. Start free at codeinspector.app.
More videos
- CodeInspector product demo (0:54)
- CodeInspector Now Works Inside Claude: Scan and Fix Code in One Conversation (video) (1:20)
- throw vs throw ex in C#: Why throw ex Destroys Your Stack Trace (video) (1:22)
- Thread.Sleep vs Task.Delay in C#: Which to Use and Why (video) (1:38)
- Task.Result and .Wait() Deadlocks in C#: Why Sync-over-Async Hangs (video) (1:47)
- ILogger Best Practices in .NET: Structured Logging That Helps You Debug (video) (1:20)