Source

Development

Branching strategy and issue tracking.

Branching

This repository uses trunk-based development. main is the trunk and is always expected to be releasable.

Work lands through short-lived branches and pull requests into main. The CI pipeline runs on those pull requests and on every push to main. Infrastructure, application, and UI deploys are started separately when the dev environment needs a new drop. See Deployment.

Issues

Open work items are tracked on GitHub Issues. This was chosen over Github Projects to keep things simple. As I am effectively a team of one - a straightforward list of requirements is sufficient.

https://github.com/PhilipTodd/mining-event-sourcing-reference/issues