There are two repos currently open, one for the frontend and backend, but the frontend version does not exist in this organization. I think it is better to keep the frontend and backend all in one repo, especially for someone (me) who has to work on both. I would rather not do 2 git pulls and 2 pull requests every time I want to work on the project. For example, auth requires me to touch both the front and backend. Therefore, I will insert all frontend work I have done in the current existing crew-connect repo. If there are any objections, let me know.
colinh09
commented
1 year ago
There are two repos currently open, one for the frontend and backend, but the frontend version does not exist in this organization. I think it is better to keep the frontend and backend all in one repo, especially for someone (me) who has to work on both. I would rather not do 2 git pulls and 2 pull requests every time I want to work on the project. For example, auth requires me to touch both the front and backend. Therefore, I will insert all frontend work I have done in the current existing crew-connect repo. If there are any objections, let me know.