Code Commits and Pull Requests
For our project, our team made the decision to host all our source code on GitHub. We split our code into two separate repositories: one for the frontend clients which rely on the Ionic framework, and one for our Express backend.
As a team, we did not really discuss the frequency at which we should be committing our code changes. However, everyone on the team has been committing at least 3-4 times a week with a pull request out for review. For pull requests, we make sure to add a description of what changes have been made to our code, as well as screenshots where applicable to better serve the reviewers. Having screenshots have been immensely helpful for reviewers, since we are able to quickly see the results of the code changes on the frontend. The code review process itself has been useful to the team as it allows us to understand and keeps us aware of what new changes have been made to the codebase. It also ensures that everyone is on the same page when it comes to our Project Plan, as everyone has to review and approve the pull request in order for it to be merged into our main branch.
Project Status
I am personally responsible for building and serving the backend REST API for those working on the frontend clients. Having an API on its own instance will allow us to consume data from any client, regardless of where it’s hosted, etc. Currently, there are a handful of CRUD endpoints that have been successfully integrated into our frontend. However, there are a few endpoints that will need further discussion amongst the team since they are more logic-heavy rather than just serving data straight from the database.
Leave a Reply