Development Workflow

Coding (Github)

Coding workflow:

• Target is at least 1 merged PR/day.
• Don't break work into artificially small commits. Medium to large PRs are preferred — AI quality is high enough and CI automation resolves conflicts and comments.
• Any PR should include the Linear link, unit/integration tests, and have CircleCI/CodeRabbit passing.
• Never push directly to master/main or staging or develop branches.
• We use the Git Flow deployment strategy.

API breaking changes:

• Discussed in #tech Slack channel.
• Separate API environment (Heroku Review Apps) created for FE to test/implement changes.
• API team coordinates PR merge with FE deployment.

Peer review for merging PRs (someone other than the requester):

• Please provide comments/screenshots/GIFs along with your PR so that the reviewer(s) can understand the intended functionality and context.
• For repos with CD (ex. Heroku auto deploy master), the PR should include the Linear issue link so that the reviewer can Deliver it.

Development Tools

Design

• Figma
  • Web - Commercial

Development

• API Explorer → Apollo Engine
  • API
• CI → CircleCI
• Code Quality → Code Climate
• iOS Certificates → Apple Developer

Hosting

• BE → Heroku, GCP
• iOS → App Store
• Android → Google Play