From ce69a08a6f13cf7d797307a64382587273311d2d Mon Sep 17 00:00:00 2001 From: Dennis Eichhorn Date: Wed, 20 Mar 2024 09:11:34 +0100 Subject: [PATCH] Update 01_Development.md Signed-off-by: Dennis Eichhorn --- Processes/01_Development.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Processes/01_Development.md b/Processes/01_Development.md index 95fe84b..baf880c 100644 --- a/Processes/01_Development.md +++ b/Processes/01_Development.md @@ -40,7 +40,7 @@ The open tasks are reviewed once a month by a senior developer. The senior devel Code changes must follow the [style guidelines](https://github.com/Karaka-Management/Developer-Guide/tree/develop/standards) (**R3**). Additionally, the automatic code style inspection tools must return no errors, failures or warnings. Developers should test their changes with inspection tools and configurations mentioned in the [inspection documentation](https://github.com/Karaka-Management/Developer-Guide/blob/develop/quality/inspections.md) in advance before submitting them for review. (**R4**) -In rare cases errors, failures or warnings during the automatic inspection are acceptable. Reasons can be for example special cases which are difficult automatize or must be individually configured in the inspection settings. If this is the case for a code change and if inspection configuration changes are necessary are decided by the senior developer performing the code review. (**R5**) +In rare cases errors, failures or warnings during the automatic inspection are acceptable. Reasons can be for example special cases which are difficult to automatize or must be individually configured in the inspection settings. If errors, failures or warnings for a code change are acceptable or if inspection configuration changes are necessary is decided by the senior developer performing the code review. (**R5**) Automated checks which are run during the review process (**R4**):