Git flow is a workflow that uses feature branching together with bug and release branching. It is widely used, and you can even find tools that support this flow by automating different parts of it. In Git flow, the master branch represents the released versions, that is, each commit in it represents a released version of the product.

The second branch is the development branch, and it serves as the integration branch for feature branches that are created from it for each feature that is developed.

When a new release is prepared, a new release branch is created from the development branch. On the release branch, stabilization and fine-tuning is done until the version is ready for release. The release is finished by merging the release branch with the master branch.

If there is a bug in the released version, a new bug fix branch is created from the master branch. All fixes are made in this branch, and it is then integrated back into the master branch (creating a new fixed version of the app) and into the development branch (to keep the bug fix for the next releases).

The following diagram depicts this:

This flow is suitable for developing apps for AppSource because the release can be isolated and you can support multiple versions of the app easily.