Skip to content

Git Branching and Pull Request Workflow

Vijaivir Dhaliwal edited this page Mar 28, 2024 · 9 revisions

This documentation is no longer being updated. For the most up to date information please visit our techdocs

Home > Developer > Contributors > Git Branching and Pull Request Workflow


image

Creating and Merging Pull Requests from partners

image

If designers are not satisfied with the UI and want improvements to be implemented by the partner developers

If the forminators team product owner declines the change. It is believed there would have been high-level conversations between the product owners which should make this scenario happen less often

  • Once the change is approved by the product owner and UI/UX designers, the forminators team developers will begin technical review.

  • The code review process will continue until the PR

is approved after all requirements are satisfied.

is declined if the reviewers think the work is not ready for a pull request

  • If the PR is approved, it will be merged into the master branch of the CHEFS Repository

  • The change will automatically deploy to the dev environment after merging the PR to the master branch.

  • Once approved, the forminators team lead will deploy the change to the test environment, where further smoke or sanity checks will be done.

  • Once the feature is ready for production, the forminators team lead will deploy it to the production environment.

Clone this wiki locally