Contributing

Branching model (Gitflow)

The repository follows Gitflow:

  • main — official release history.

  • develop — integration branch for features.

  • feature/* — one branch per feature, forked from develop, merged back into develop.

  • bugfix/* — a scoped fix branch (the repo history uses bugfix/dev-XXXX names).

  • release/* — forked from develop for release stabilisation; merged into main (tagged) and back into develop.

  • hotfix/* — forked from main to patch a release; merged into both main and develop.

Commit messages

Commits reference the JIRA key (e.g. refs: DEV-1234 / DEV-1234: <summary>). Keep the subject short and in English.

Before you push

npm test             # Vitest unit tests
npm run build        # confirm the production build compiles

Run Prettier so the diff matches the repo’s formatting (100 columns, single quotes).

Working with reusable components

Shared, standalone form controls live under src/app/components/base (ft-common-*). Prefer extending or reusing these over adding raw HTML controls, so behaviour (validation, disabled/loading states, tooltips) stays consistent.

Related pages

The repository README covers the local development workspace (clone, install, ng serve).