🤔 What's the problem you've observed?
We are currently publishing of branches. This results in a large number of branches in each repository. We are not using tags, when we created our release process tags could not be protected.
This is no longer the case.
✨ Do you have a proposal for making it better?
- Protect tags (already done).
- Add tags to the protected Release environment.
- Switch all the release actions to trigger on a pushed tag. Either
v[0-9]+.[0-9]+.[0-9]+ or go/v[0-9]+.[0-9]+.[0-9]+.
- Stop creating release branches with polyglot-release.
- Remove all release branches
- Remove release branches from the protected Release environment.
📚 Any additional context?
No response
🤔 What's the problem you've observed?
We are currently publishing of branches. This results in a large number of branches in each repository. We are not using tags, when we created our release process tags could not be protected.
This is no longer the case.
✨ Do you have a proposal for making it better?
v[0-9]+.[0-9]+.[0-9]+orgo/v[0-9]+.[0-9]+.[0-9]+.📚 Any additional context?
No response