From 80808d42c257823feb873f80d06b325430c9350e Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 8 Feb 2026 10:09:42 +0200 Subject: add per-project .hexaiconfig.toml config override and lower coverage target to 80% MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Introduce support for a .hexaiconfig.toml file at the git repository root that selectively overrides the global config. Precedence order: defaults → global config → project config → env vars. Also lower the coverage threshold from 85% to 80%. Co-Authored-By: Claude Opus 4.6 --- AGENTS.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'AGENTS.md') diff --git a/AGENTS.md b/AGENTS.md index 598b0f8..4009b7f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -10,7 +10,7 @@ - Avoid duplication of code when the functions are larger than 5 lines. - If possible, construct individual methods so that they can be unit tested. But only if it doesn't add too much boilerplate to the code base. -- Aim for at least 85% unit test coverage of all source code. The command to check the coverage is "mage coverage" +- Aim for at least 80% unit test coverage of all source code. The command to check the coverage is "mage coverage" - Ensure that all unit tests pass before commiting any changes. - Always run the gofumpt code reformatter on all go files modified. - There should be no source code file larger than 1000 lines. If so, split it up into multiple. @@ -25,3 +25,4 @@ - Whenever incrementing the version, update the version number in the project, commit to git, tag the version and push to git. - When a major feature was introduced, increment ?.X.? - When only minor changes were done or only bugs were fixed, increment the version as ?.?.X + -- cgit v1.2.3