Add EF Core 8 Migrations to a .NET 8 Class Library
Step-by-step guide to adding EF Core 8 migrations in a .NET 8 class library, covering DbContext setup, CLI commands, runtime application, and idempotent script generation for CI/CD.
Loading…
ReadMeFeed / Community knowledge
#ci-cd
Real questions. Useful conversations. Find the people who know your stack.
Automating CI/CD Failures with SonarQube Quality Gates
Implement SonarQube Quality Gates to automatically fail CI/CD builds when new code breaches thresholds for bugs, vulnerabilities, or coverage.
sonarqubeBazel Caching Without Rebuilding Everything: Disk Cache, Remote Cache, and Hermeticity
Reuse Bazel action outputs across machines and CI runs with --disk_cache and --remote_cache, but only if your actions stay hermetic.
bazelArchitecting Reusable CI/CD Logic with CircleCI Orbs
Learn how to encapsulate shared CI/CD logic using CircleCI Orbs to eliminate configuration drift across multiple repositories while maintaining security boundaries.
circleciDiagnosing GitHub Actions GITHUB_TOKEN Permission Failures
A diagnostic guide for GitHub Actions jobs that fail because GITHUB_TOKEN lacks the required repository permissions.
githubactionsDiagnosing Common Failures in Postman Collection Runner and Newman CLI
When a Postman collection stops running in the UI or in a CI pipeline, the root cause can be a network issue, data file format, or a sandbox difference. This guide walks through the most common failure modes, shows how to identify them, and gives concrete fixes and escalation thresholds.
Clean as You Code: Making SonarQube Quality Gates Actually Work
Your SonarQube quality gate fails on legacy code, so the team ignores it. Here is how to scope enforcement to New Code, use branch analysis, and verify the result in CI.
Keep protected branches green with GitLab merge trains
Merge trains serialize merge requests against the current branch tip so each change is validated before it lands, reducing broken-main incidents.
gitlabDiagnosing Forgejo Actions Runners That Stay Pending or Never Start
A step-by-step diagnostic guide for Forgejo self-hosted Actions runners that stay pending: verify runner heartbeat, workflow triggers, concurrency limits, and label matching — with concrete fixes and escalation criteria.
forgejo