Skara is currently rather vulnerable to badly formatted .jcheck/conf files. If for example the version value doesn't parse, it will cause notification errors that get stuck in retry loops, which is very disruptive.
To help mitigate this, it would be nice if jcheck could step in and protest if a commit has a badly formatted .jcheck/conf in it. That would create a blocker in any PR trying to integrate such change.
To help mitigate this, it would be nice if jcheck could step in and protest if a commit has a badly formatted .jcheck/conf in it. That would create a blocker in any PR trying to integrate such change.