Closed ellisio closed 3 years ago
@zeke Can we please get some feedback on this? 🍻
@zeke Hey man, better late than never I guess... Been crazy in my world. Anywho, just pushed up new commit with the simplified approach.
enabled: false
status: success
and a message that the check is skipped.
Our organization allows engineers to create microservices using Spotify's Backstage developer portal. All of these services follow conventional commits. However, we have some repositories in our organization (Helm Charts) that use other release strategies.
We don't want to have to switch to manually adding a newly created service to this configuration every time someone creates a new microservice from Backstage. Instead, we'd rather "opt out" of this merge check on a per-repo basis.
This adds the
enabled
configuration option, which defaults totrue
to avoid breaking changes. This would allow organizations in our situation the ability to setenabled: false
in.github/semantic.yml
to disable this merge check.