How to deal with API clients, the lazy way — from code generation to release management
.The release procedure. To relieve the release procedure and to much better arrange the code, each API customer has its own repo: you’’ ll discover Python code in https://github.com/arduino/iot-client-py, Go code in https://github.com/arduino/iot-client-go and so on etc. When Apigentools completes its run, you wind up with brand-new branches including the most recent updates pressed to each one of the customers’ ’ repositories on GitHub. As the branch is pressed, another GitHub workflow begins (see the one from the Python customer as an example) and opens a Pull Request, asking to combine the modifications on the master branch. The maintainers of each customer get a Slack notice and are asked to evaluate those Pull Requests –– from now on, the procedure is primarily manual.