Closed yanick closed 7 months ago
I've merged #193 to main so that we have an active semantic checker, but it seems that setting the config of Semantic Pull Request to disable
is not enough to keep it at bay. The problem is that I don't know whose account has enabled that service for this repo. So until we find that, I guess we'll have to merge things using the override.
(and I changed the config of the repo so that squashed merges use the title of the PR as their commit message, so that the whole semantic stuff work)
@yanick do you have access to the repository settings? The "Semantic Pull Requests" requirement is set - and thus can be removed - via branch protection rules on the main
branch.
If not, do you know who we could ping that does have admin access to the repo? This is gonna be quite annoying for continuing maintenance
I do, I do have access to the settings! \o/ I must have gotten those powers when I submitted changes to the documentation repo. I'll go and peek in the config after breakfast.
Aaaand it should be disabled, now. We'll see for sure at the next PR. :crossed_fingers:
PRs have been running smoothly 🚢, I think we can call this one resolved
Yup. Closing!
https://github.com/zeke/semantic-pull-requests#readme
And indeed it doesn't seem to be running at all.
From the README, it seems we should be able to add a
semantic.yml
file withenabled: false
to bypass the action. But we also need to add a replacement (the README also has alternatives. Must look at them)