Automated Release

[mcaulifn]

It would be helpful to automate releases using something like https://github.com/semantic-release/semantic-release.

[npalm]

@mcaulifn the release almost fully automated, we only need to merge back in the master branch. Release is done via semantic release. See the workflow for the release for some details.

[mcaulifn]

Is it worth looking at automating a PR creation whenever a PR with some criteria is merged to develop?

[npalm]

I would love more automation, not liking the manual work. But at the moment we verify PR's with a bigger impact. Typically on the labmda code manual with a real deployment. In general the unit tests have a good coverage. But mocking is not always good enough to check if the system is working as it should be.

Maybe you have any thought on how we could setup a real end to end check. But for security reason we prefer also to have a manual inspection before we run the actual deployment.

Any suggestion on how to improve automation is welcome. I was also thinking about auto merge develop (for example once a day) or even remove the layer of develop.

[mcaulifn]

Internally, we require formatted commits (thus why mine are that way) and then releases are cut when the PRs are merged.

I think a workflow that would auto create a PR for master <- develop when a PR is merged to develop might work. That would prompt some additional testing/deployments.

FWIW, I make sure to work on the tests when I submit PRs 😄