finos / finos/common-cloud-controls
Release Action
- Dominant language
- Go
- Stars
- 87
- Forks
- 80
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 13
Description
## Feature Request
### Description of Problem:
We need to simplify and streamline the CCC release process - we haven't done any releases in a long time and it's over-complicated.
### To Do
- [ ] Build a release action that works when PRs are merged: It should release to GitHub Releases + Eddie's new release repository.
- [ ] Go code should be released to go github releases with the right tags.
- [ ] Update documentation / governance for the project on how releases are done - we should be saying that if the code is approved into the main branch, then releases can (and should automatically) happen.
CCC Releases should use the CalVer format as we've agreed before. This should happen automatically on merge.
Contributor guide
Assessment
This issue has not been assessed yet.