Bring back black and prefer make lint over a custom action

.github/workflows/build.yml

@@ -35,8 +35,11 @@ jobs:
       - name: Install development dependencies
         run: make dev
 
-      - name: Run linter (ruff)
-        uses: chartboost/ruff-action@v1
+      - name: Check code formatting
+        run: make format-check
+
+      - name: Run linter
+        run: make lint
 
       - name: Run aleph tests
         run: make ALEPH_TAG=${GITHUB_SHA} test

CONTRIBUTING.md

@@ -54,7 +54,7 @@ Aleph uses two main branches. The **develop** branch is for any new work that ne
 
 ### Code Formatting and Linting
 
-We use automatic code formatters and linters to keep our code consistent and to spot bugs and style issues early in the process. For Python code, we use [ruff](https://beta.ruff.rs/). Our JavaScript code base uses [Prettier](https://prettier.io) and [ESLint](https://eslint.org/).
+We use automatic code formatters and linters to keep our code consistent and to spot bugs and style issues early in the process. For Python code, we use  [black](https://black.readthedocs.io/en/stable/) and [ruff](https://beta.ruff.rs/). Our JavaScript code base uses [Prettier](https://prettier.io) and [ESLint](https://eslint.org/).
 
 When you open a pull request, your changes are automatically checked for consistency with our code formatting and linting rules. You can also run the checks in your local development environment. If you aren’t familiar with these tools yet, don’t worry. You can open a pull request even if your changes don’t pass these checks.
 

Makefile

@@ -32,9 +32,15 @@ lint:
 lint-ui:
 	$(UIDOCKER) npm run lint
 
+format:
+	black aleph/
+
 format-ui:
 	$(UIDOCKER) npm run format
 
+format-check:
+	black --check aleph/
+
 format-check-ui:
 	$(UIDOCKER) npm run format:check