Skip to content

Commit

Permalink
Enable bracket expansion and add init-githooks make target
Browse files Browse the repository at this point in the history
  • Loading branch information
SimonBaeumer committed Sep 17, 2024
1 parent 31664b8 commit fa6dadc
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 1 deletion.
2 changes: 2 additions & 0 deletions .clang-format
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ PointerAlignment: Left

IndentPPDirectives: AfterHash

InsertBraces: true

IncludeBlocks: Regroup
IncludeCategories:
- Regex: '^((\"|<)(api|internalapi|storage)/)'
Expand Down
3 changes: 3 additions & 0 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,9 @@ shellcheck-all-dockerized:
docker build -t shellcheck-all $(CURDIR)/utilities/shellcheck-all
docker run --rm -v "$(CURDIR):/scripts" shellcheck-all:latest

.PHONY: init-githook
init-githook:
git config core.hooksPath ./githooks/

# This defines a macro that can be used to add pre-commit targets
# to check staged files (check-<linter name>) or all files (check-<linter name>-all)
Expand Down
2 changes: 1 addition & 1 deletion docs/how-to-start.md
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@ Even though development containers is a supported feature of `Docker for Desktop
### Setting up git hooks

Git hooks are configured in the `.pre-commit-config.yaml` file using [pre-commit](https://pre-commit.com)
In order to use them install pre-commit, and run `git config core.hooksPath ./githooks/` from the collector root directory.
In order to use them install pre-commit, and run `make init-githook` from the collector root directory.

## Run in Minikube
### Build the collector image
Expand Down

0 comments on commit fa6dadc

Please sign in to comment.