![]() We have so many different branches, when merging branches from one category to another different scripts are needed: feature-to-develop, develop-to-release, release-to-main, hotfix-to-main, main-to-develop, develop-to-feature, etc… Conflicts would show up everywhere! And they cannot be solved via automation scripts. It was a mess to use or manage the CI/CD scripts. Soon after CI/CD was implemented we found that our work process did not get any faster. We were following Git-flow to manage our source code and development progress. We introduced Continuous Integration and Continuous Deployment (CI/CD) practice into the team to help us reduce repetitive work.ĬI/CD is a method to frequently deliver apps to customers by introducing automation into the stages of app development. Through automation, the process of kaizen can be sped up rapidly.Ĭommitting source code is a daily job for engineers, it’s not just about handing over our daily work but also testing the code in our server environment. With customer feedback and analytical data, there are numerous amount of improvements that we can do to better serve our customers. AttemptĪs part of the Toyota group companies, we implement the principle of improvement (or kaizen in Japanese) in our daily work. This article shares why and how we changed our workflow from Git-flow to GitHub-flow. For the greater benefits, apart from the service we provide, workflow is also where we need to improve. ![]() ObjectiveĪs a startup company, there are a lot compromises within our first generation product. You can read more about the Global group here. ![]() I work as a full-stack engineer in Global KINTO App team. This is Ruoyang Wen from Global Group, KINTO Technologies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |