Developer Resources

Repository Structure & Permissions

Repository Types

RMC maintains multiple repositories for different purposes:

• Web applications (React frontend, ASP.NET backend)
• Desktop tools (WPF applications)
• Libraries/packages (C# models, shared utilities)
• Data science tools (Python, R scripts)
• Documentation (Docusaurus sites)

USACE-RMC GitHub Enterprise Structure

Access Model: RMC uses a centralized administrative model where repository administration is handled by Organization Owners, with Write access delegated to developers as needed.

Roles and Permissions

GitHub Role	Who Has It	Permissions	Responsibilities
Organization Owner	Organization owners and repository administrators	Full admin access to all repositories, organization settings, approve/merge PRs	Review and approve PRs, merge to main, manage repository settings, organization administration
Member (Write)	Developers assigned to specific repositories	Create branches, push commits, create PRs, review code	Develop features, create pull requests, review peer code
Member (Read)	All 31 organization members (base permission)	View and clone all repositories	Read code, observe development, learn from codebase
Outside Collaborator	10 external contributors on specific repos	Read or Write access to assigned repositories	Contribute to specific projects as assigned

Permission Rules

Organization Owners and Repository Administrators:

• Have administrative access according to current organization and repository settings
• Merge to protected branches where repository policy grants that authority
• May approve and merge their own PRs when necessary (use discretion - get a second review when possible)
• Can modify repository settings and branch protection rules
• Can override branch protection in emergencies (use sparingly)

Members with Write Access:

• Can create feature branches and push commits
• Can create pull requests
• Cannot merge to protected main branch without owner approval
• Can review and comment on pull requests
• Should have Write access on repositories they actively contribute to

All Members (Base Read Permission):

• Can view and clone all organization repositories
• Can observe development across all projects
• Promotes transparency and learning across the team

Protected Branch Rules:

• Follow the current required checks and approvals configured for each repository.
• Direct commits to protected main are prohibited.
• All changes use the pull request workflow.

In the RMC Software Documentation repository, administrators classify every PR and may fill any review role. Formal document stages use one named reviewer each, with non-admin author and cross-stage identity restrictions. See the repository-specific workflow.