Skip to content

Development Workflow

Jump to bottom
Mangat Singh Toor | ਮੰਗਤ ਸਿੰਘ ਤੂਰ edited this page Aug 17, 2025 · 3 revisions

Branching Strategy

There is a development stage and production stage for Airbnb-regulation project (CodeName: PolicyScout). We plan to maintain two official branches for this project:

  • development
  • main

The deployment target for development branch is the development stage and the deployment target of main branch is the production stage. We will take do manual release deployments from development to main branch using github tags marking each release with release notes.

Developers will create their own feature branches and merge them in development after raising the pull request.

Here's a revised and improved version of the Secret Handling Strategy section:

Secret Handling Strategy

We employ different secret management approaches for development and production environments. In the future, there will only be one approach.

Development Environment

  • Storage: Secrets are stored in GitHub Secrets
  • Access: Secrets are imported during deployment via GitHub Actions
  • Environment Variables: The development environment is configured using these GitHub-stored secrets

Production Environment

  • Application Secrets: Stored securely in S3 buckets with appropriate encryption and access controls
  • AWS Credentials: Stored in GitHub Secrets for deployment automation
  • Runtime Access: During deployment, application secrets are downloaded from S3 to the EC2 instances

Clone this wiki locally