Skip to content

Conversation

@franziska-denk
Copy link
Collaborator

What?

To automatically scan pushes and pull requests for secrets with gitleaks, this PR introduces the corresponding action YAML under .github/workflows/pre-commits.yaml. It also introduces changes needed to satisfy the formatting requirements in the .pre-commits-config.yaml, as standard measures to ensure clean code.

Why?

We want to ensure that no secrets (and badly formatted code) can be added to the codebase.

How?

The .github/workflows/pre-commits.yaml-file holds a standard workflow that runs the .pre-commits-config.yaml file on push and pull requests.

Testing

I tested this by making sure my pushed commits are accepted by the new workflow. ✅

image

Copy link
Contributor

@kevinconka kevinconka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

very nice 😎

Copy link
Contributor

@kevinconka kevinconka Jan 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool! I did not think of using pre-commit to do all the linting and formatting checks

@franziska-denk franziska-denk merged commit 59159b2 into develop Jan 22, 2026
3 checks passed
@franziska-denk franziska-denk deleted the feature/gitleaks-action branch January 22, 2026 07:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants