-
Notifications
You must be signed in to change notification settings - Fork 0
02. Tooling & Setup
This section describes the tools and technical setup used to manage the software lifecycle of the project.
GitHub is used as the central platform for development and lifecycle management.
The following GitHub features are used:
-
Repository
Stores the complete source code of the project. -
Wiki
Contains the software lifecycle documentation, including workflow descriptions and screenshots. -
Issues
Used to track user stories and tasks. -
Pull Requests
Used to integrate feature branches into the main development branch and to trigger CI/CD pipelines.
The project uses GitHub Projects as a Kanban board to manage the workflow.
The Kanban board represents the current state of user stories and supports visual tracking of progress.
Typical columns include:
- Backlog
- To Do
- In Progress
- Review
- Done
Each user story is moved across the board according to its current lifecycle state.
The project follows a feature branch-based branching model.
-
main
Contains the stable version of the project. -
feature/*
Used for implementing individual user stories or tasks.
Each user story is implemented in a separate feature branch, which is later merged into main via a pull request.
The project uses CI/CD pipeline automation to ensure code quality and consistency.
- CI/CD pipelines are configured using GitHub Actions
- Pipelines are automatically triggered on:
- pull request creation
- updates to pull requests
- Typical automated steps include:
- build execution
- automated checks (e.g. tests or validations)
The CI/CD pipeline ensures that changes are verified before being merged and integrates automation into the software lifecycle.
The combination of GitHub repositories, project boards, branching strategies, and CI/CD automation provides a structured and traceable software lifecycle management setup.