Skip to content

refactor: Use prek workspaces#1236

Open
Techassi wants to merge 1 commit into
mainfrom
refactor/use-prek-workspaces
Open

refactor: Use prek workspaces#1236
Techassi wants to merge 1 commit into
mainfrom
refactor/use-prek-workspaces

Conversation

@Techassi

Copy link
Copy Markdown
Member

Triggered by #1233.

prek supports nested configs (called workspace mode) which enables us to use indivudal, crate specific config files. Those hooks are only triggered if there are changes in the subdirectoy which drastically cuts down on runtime during commit and in CI.

Currently, most of these configs are copy+pasted and we ideally want some kind of central config + input based on the prek project/workspace member to avoid this duplicated code. This was already raised as an issue upstream.

prek supports nested configs (called workspace mode) which enables
us to use indivudal, crate specific config files. Those hooks are
only triggered if there are changes in the subdirectoy.

Currently, most of these configs are copy+pasted and we ideally want
some kind of central config + input based on the prek project/workspace
member to avoid this duplicated code. This was already raised as an
issue upstream.
@Techassi Techassi self-assigned this Jun 29, 2026
@Techassi Techassi moved this to Development: Waiting for Review in Stackable Engineering Jun 29, 2026

@NickLarsenNZ NickLarsenNZ left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Does pre-commit support this?

Most users currently run pre-commit. If only prek supports this, then we probably need some kind of announcement before this gets merged.

@Techassi

Copy link
Copy Markdown
Member Author

No, this is prek specific, see https://prek.j178.dev/workspace/.

So yes, this would need to be announced.

@NickLarsenNZ

Copy link
Copy Markdown
Member

Let's wait until everyone has had time to update.

@Techassi Techassi moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Jun 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: In Review

Development

Successfully merging this pull request may close these issues.

2 participants