Deft Workflow on Mainline

Workflow Style

All developers work on the mainline, frequently (e.g. many times a day) pushing changes from their local branches into the mainline and merging changes from the mainline into their local branch to ensure their branch does not diverge.

To Create New Issues

When new issues are created, the new issues are committed/pushed to the mainline, so that everyone can see them when they next pull down the latest changes.

Working on Features

When a developer starts working on an issue, they change its status to "in-progress", or some other pre-agreed status, and commit/push the change to the mainline so that everyone can see what they are doing.

Then they modify the code, committing/pushing working code frequently to the mainline.

When the feature is implemented, they mark its status as "implemented" (or "ready-for-testing" or some other status depending on how the project is organised) and commit/push the change to mainline so that everyone can see that the work is done.