PR FIXUP - Remove mock regen from ci

I'm still in favour of this in the short term, but it is too controversial and is bogging down the highly desired `make mock` command.
sourcenetwork · Jul 6, 2023 · b71916b · b71916b
1 parent 1c16e70
commit b71916b
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 2 deletions.
diff --git a/Makefile b/Makefile
@@ -171,7 +171,6 @@ test\:build:
 
 .PHONY: test\:ci
 test\:ci:
-	@$(MAKE) mock
 	DEFRA_BADGER_MEMORY=true DEFRA_BADGER_FILE=true $(MAKE) test:names
 
 .PHONY: test\:go

diff --git a/tests/README.md b/tests/README.md
@@ -23,7 +23,7 @@ These tests focus on small, isolated parts of the code to ensure each part is wo
 For unit tests, we sometimes use mocks. Mocks are automatically generated from Go interfaces using the mockery tool. 
 This helps to isolate the code being tested and provide more focused and reliable tests.
 
-To regenerate the mocks, run `make mock`.  `make test:ci` will also do this.
+To regenerate the mocks, run `make mock`.
 
 The mocks are typically generated into a separate mocks directory.