Repository navigation
The Development Journey
Link to our Miro Board: https://miro.com/app/board/uXjVLS4P3ls=/
- Feature branch:
feature/<ticketid>-<title> - Bugfix:
fix/<ticketid>-<title> - Release:
release/<version>
Example branch from ticket:
feature/430-implementing-language-file
- https://www.geeksforgeeks.org/how-to-naming-conventions-for-git-branches/
- https://graphite.dev/guides/git-branch-naming-conventions
The branches are protected by a GitHub ruleset. Changes to the main and dev branches can only be made via a pull request, which must be reviewed by at least two developers. There are also checks in place for testing, linting, and formatting that must pass before a pull request can be approved. Changes to the main branch are automatically published to the container registry.
The backend of the application is supported by automated E2E tests as well as unit tests. Before a pull request can be approved, all tests must pass. Manually, the backend was tested using OpenAPI/Swagger. The test coverage for the backend is approximately 80%.
