GitHub Guidelines for Mobile Teams

Mobile repos have unique risk: native folders, signing configs, and large binary assets. GitHub settings and templates enforce consistency across contributors.

Repository standards

Mobile repos have unique risk: native folders, signing configs, and large binary assets. GitHub settings and templates enforce consistency across contributors.

Pull request lifecycle

Required repository configuration

Branch protection on main: require PR, dismiss stale reviews, require status checks (lint, test, android-build).
CODEOWNERS: @mobile-leads for ios/, android/, fastlane/, .github/workflows/.
PR template: screenshots/video, test plan, version impact, devices tested, migration notes.
Issue templates: bug (steps, OS, build version), feature, release checklist.
Dependabot: enable for npm and bundler (Fastlane); review native dependency bumps in android/build.gradle.
Never commit: prod google-services.json, .jks keystores, .p12 certificates, API keys.

PR review checklist for reviewers

Does this change need a native rebuild? (new package with native code = yes)
Are testID props added for new interactive UI (Detox)?
Does Android need ProGuard keep rules? Does iOS need Info.plist entries?
Will this change require a MAJOR/MINOR/PATCH version bump?
Are screenshots attached for UI changes?