Decided

In the development of the project, we need to choose a source code hosting platform to store and manage our project's codebase. Several options were considered, including GitHub, GitLab, Bitbucket, and self-hosted solutions. Each option offers its own set of features, integrations, and accessibility considerations.

We have decided to use GitHub as the source code hosting platform. This decision was primarily based on the availability of GitHub Actions for continuous integration and deployment (CI/CD) workflows. Additionally, while the ZHAW's GitHub was considered, it was determined that access to GitHub Actions would not be available on that instance, leading us to choose the public GitHub platform instead.

• Integration with GitHub Actions: By choosing GitHub, we gain access to GitHub Actions, a powerful CI/CD platform that allows us to automate build, test, and deployment processes directly from our GitHub repository.
• Community and collaboration: GitHub is widely used by developers and organizations worldwide, providing a familiar and collaborative environment for team members to contribute, review code, and manage projects as Public Repository: Opting for the public GitHub platform means our project's code will be publicly accessible unless we choose to pay for private repositories. While this may not be suitable for all projects, it aligns with the open-source nature of many software development projects and encourages transparency and community involvement.
• Access to additional GitHub features: In addition to GitHub Actions, GitHub offers a range of features and integrations such as issue tracking, pull requests, code reviews, and project boards, which can enhance our development workflow and project management capabilities.