09. deployments: git

Epycbyte and Git Deployment Overview

1. Project Setup and Production Branch Selection:

   • When creating a new project from a Git repository, Epycbyte automatically selects the production branch based on the presence of main or master branches. If these are absent, it uses the Git repository's default branch setting.

2. Team Management and Deployment Permissions:

   • Hobby Teams: Only team owners connected via their Git account can deploy commits. This ensures that non-owners cannot push changes unless they become members of a Pro team.
   • Pro Teams: Members can deploy after being added, with the commit author's identity checked against the team's Login Connections.

3. Pull Requests and Authorization:

   • After forking a public repository, pull requests may require authorization if they modify epycbyte.json or environment variables. This is a security measure to prevent sensitive information leaks.
   • If the commit author is already a team member, the authorization step is skipped.

4. Preview Branches and Phases:

   • Default Preview: Changes pushed to non-production branches (e.g., main) are served through preview domains like url-composition.project-name-branch.epycbyte.app.
   • Multiple Phases (e.g., Staging): Additional Git branches can be created to assign specific domains and environment variables, allowing for testing before merging into production.

5. Merging and Branch Management:

   • After testing in preview phases, changes are merged into the production branch. Preview branches are typically kept active for future use unless deleted.