Block a user
Setu up fully automated PR merges
Not sure how that helps achieving full automation. Someone still has to assign that label, right? And also the job triggered by that label has to be able to trigger a merge.
templates: add template for enw clan
templates: add template for enw clan
clan-cli: dev-shell, build, tab completion, formatting, linting, unit tests
Yes, currently it's set to require 100% coverage. You can then exclude functions from the coverage report via this comment. I thought, requiring tests for newly added functions is a better default…