How to implement Microsoft BCQuality in your GitHub Pull Request

Key points

• BCQuality is a reference library covering AL code quality best practices in correctness, maintainability, readability, performance, and testability
• GitHub agentic workflows can automatically review AL code changes and post advisory comments on pull requests
• Implementation requires three steps: copy the workflow file, place it in .github/workflows/, and compile it with gh aw compile
• The workflow can use either the public Microsoft BCQuality repository or a private internal clone with proper authentication
• Reviews are advisory only and do not block merges, providing additional review coverage without disrupting development flow

Quotes

• “Think of it as a reference library for Business Central best practices around correctness, maintainability, readability, performance, and testability.” (Defines what BCQuality provides as a knowledge base for consistent code quality standards)
• “It does not block your merge. It gives your team another set of eyes.” (Explains the non-intrusive nature of the review process, allowing teams to maintain development velocity)
• “If you already use pull requests for AL changes, this is an easy upgrade.” (Shows that adoption fits naturally into existing workflows with minimal friction)

Context

• Features: BCQuality advisory review, agentic workflow integration, pull request automation, AL code quality checking

Source: That NAV Guy, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.