Ship faster with automated quality signals to identify defects, monitor test coverage, and enforce checks during pull requests.
-
Who is this for: Intermediate GitHub users who want quality checks that support team velocity.
-
What you'll learn: How to enable Code Quality, publish coverage, and enforce thresholds with rulesets.
-
What you'll build: A quality enforcement flow for a school activities site.
-
Prerequisites:
- Recommended: Introduction to Repository Management
- Recommended: GitHub Copilot Code Review
- Comfort creating pull requests and editing repository settings
- Familiarity with basic GitHub Actions concepts
-
How long: This exercise takes less than 45 minutes to complete.
In this exercise, you will:
- Enable Code Quality and preview standard findings.
- Open a pull request to start remediating a quality issue and view feedback from AI findings.
- Add pull request coverage reporting as a test confidence signal.
- Enforce quality and coverage thresholds with rulesets, explore evaluate mode, then confirm the fix and merge.
Simply copy the exercise to your account, then give your favorite Octocat (Mona) about 20 seconds to prepare the first lesson, then refresh the page.
Important
GitHub Code Quality is currently only available for organizations with Code Quality enabled. It is not available on personal accounts. To use this exercise, you must copy the exercise to an organization with Code Quality enabled.
Having trouble? 🤷
When copying the exercise, we recommend the following settings:
-
For owner, choose your personal account or an organization to host the repository.
-
We recommend creating a public repository, since private repositories will use Actions minutes.
If the exercise isn't ready in 20 seconds, please check the Actions tab.
-
Check to see if a job is running. Sometimes it simply takes a bit longer.
-
If the page shows a failed job, please submit an issue. Nice, you found a bug! 🐛
© 2025 GitHub • Code of Conduct • MIT License