Chapter 18: Contributing to the AL Community

Objectives

By the end of this chapter you will be able to:

• Contribute meaningful improvements to AL repositories
• Write contribution artifacts that are technically useful, beyond cosmetic fixes
• Collaborate through issues, pull requests, and review feedback
• Evaluate contribution quality against clear standards

18.1 Contributing to open source AL projects

The most useful contributions are usually:

• bug fixes with steps to reproduce the bug,
• tests that prevent regressions,
• performance or security improvements,
• documentation updates tied to how the code behaves.

An open source AL project you can contribute to:

• BCApps, Microsoft’s repository for the Business Central application platform: the System Application, the Base Application, and Microsoft’s first-party apps

18.2 Pull request quality standards

A strong contribution should include:

1. Problem statement: what was wrong and why it matters.
2. Change summary: what was modified and where.
3. Validation evidence: tests, repro output, or before/after behavior.
4. Risk notes: known limitations or follow-up tasks.

Avoid low-impact PRs that only fix an isolated spelling mistake and add no technical value.

18.3 Writing helpful documentation and tutorials

Write documentation that a developer can act on, not only read:

• Use runnable examples.
• Explain assumptions and prerequisites.
• Link related chapters or objects so readers have the context.

Chapters 9, 11, and 16 of this book are good models of this structure.

18.4 Community collaboration habits

• Open a clear issue before making large design changes.
• Respond to review feedback with evidence, not opinion.
• Keep discussions respectful and focused on solutions.

Chapter summary

In this chapter you:

• Learned how to make AL contributions that are technically meaningful
• Applied concrete quality criteria to pull requests
• Practiced documentation patterns that support implementation
• Built contribution habits that keep community collaboration maintainable

Tasks

1. Contribution assessment. Review one AL PR and score it against the four quality standards in 18.2.
2. Improvement proposal. Draft a high-value issue that includes reproducible steps and expected behavior.
3. Documentation task. Update one technical section so another contributor can execute it without extra context.
4. Try it yourself. Write one paragraph explaining why test evidence is more persuasive than screenshots alone.

Check your work: your contribution checklist should be specific enough to evaluate this book’s chapter tasks and reference solutions.