Developer Resources

Overview

Purpose

This document establishes standardized workflows for the development team to ensure:

• No overlapping work: Developers work on isolated branches for specific features
• Code quality: Changes meet the review policy defined for their repository and classification
• Clear history: Commit messages and PR descriptions provide context
• Non-breaking changes: Main branch remains stable and deployable
• Consistent AI assistance: AI assistants follow team standards

Core Principles

1. Main branch is always deployable - Never commit breaking changes directly to main
2. One feature, one branch - Each feature/bug/enhancement gets its own branch
3. Follow repository review policy - Required checks and reviewers depend on the repository and change classification
4. Clear communication - Commit messages and PRs tell the story of why changes were made

For the RMC Software Documentation repository, use the Documentation Guide review workflow. It supersedes generic reviewer-count guidance in this cross-project SOP.