Skip to Main content

Backend Development Workflow

This page covers the regular backend workflow for Precise Alloy: which branch to start from, how branches should be named, and how changes move through the integration, preparation, and production environments.

Branching

  • The base branch for all backend work should be master.

  • When creating a branch for a new feature, use the format features/{ticket-id}-feature-name.
    Example: features/ABC-123-contact-block

  • For bug fixes, follow the pattern bugfixes/{ticket-id}-issue-name.
    Example: bugfixes/ABC-456-contact-block-header-issue

Apart from features/* and bugfixes/*, there are also infra/* and refactor/* branches.

Notes:

  • Always use the task or bug ID as the ticket ID. Do not use the user story ID, because it is shared between the frontend and backend teams.

  • Every branch should include the ticket ID and a short description so its purpose is clear without opening Jira and reconstructing history from fragments.

  • Delete your branch after it has been merged into the base branch, unless there is a compelling reason to keep it.

Deployment

Whenever changes are pushed or merged into the inte branch, it will initiate the deployment process to release the code into the INTE environment.

Whenever changes are pushed or merged into the prep branch, it will initiate the deployment process to release the code into the PREP environment.

Whenever changes are pushed or merged into the prod branch (or master/main, depending on your project's configuration), it will initiate the deployment process to release the code into the PROD environment.

While it's possible to deploy to the PREP and PROD environments by transferring the deployment package from lower environments through the PaaS Portal, it's advisable to prefer deployment via pipelines for consistency and reliability.