Skip to content
This repository has been archived by the owner on Sep 11, 2022. It is now read-only.
/ airtegal Public archive

HAHAhahahhaHHAhha........

Notifications You must be signed in to change notification settings

hpj/airtegal

Repository files navigation

Netlify Status test deploy

This project will be following an abridged version of Gitflow

Branch name for production releases: [release]
Branch name for "next release" development: [development]


Each new feature should reside in its own branch, which can be pushed to the central repository for backup/collaboration. But, instead of branching off of main, feature branches use develop as their parent branch. When a feature is complete, it gets merged back into develop. Features should never interact directly with main


The overall flow of Gitflow is:

  1. Feature branches are created from development
  2. When a feature is complete it is merged into the development branch
  3. When there's enough changes the development branch is merged into release
  4. If an issue in main is detected a hotfix branch is created from release
  5. Once the hotfix is complete it is merged to both development and release