Ryukyo
commented
4 years ago If we want to go with CircleCI I can prepare a project, since I think I need to sign up the repository. And then invite collaborators Depending on our priorities after MVP we should start preparing a pipeline with some tests and need to see who wants to do it. The earlier we have the tests, the earlier we can profit of them
Script
I want to write frequently used commands (such as firebase deploy) in package.json.
CI/CD
It's a pain in the ass to have to check that everyone works properly locally after merging into development, so I'd like to make it so that it will be automatically lint/format, built (mainly forntend), tested and deployed after the merge.
However, with the current per-name branch model, we need to merge periodically or you'll end up in conflict hell.
E2E Test
When the number of features increases, leaving it to manual testing will slow down the degrading find process, and it will take longer to resolve. I feel like writing a lot of Unit Tests would be delicate for the duration and size of this project, so I feel like it's better to write basic E2E tests so that we can do automatic regression testing.
Transparency
If we leave it to the Tech Lead alone to figure out what's going on, they usually die of stress, so we want to make sure that everyone knows what we do and what's happening in the team's work and what changes are happening right away.
Trello Kanban, Slack Integration, etc.