Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CT-104] use pre-commit to manage code checks (enforce styleguide, code formatting, type checks) #3196

Closed
kwigley opened this issue Mar 25, 2021 · 2 comments
Assignees
Labels
jira tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality

Comments

@kwigley
Copy link
Contributor

kwigley commented Mar 25, 2021

pre-commit is a tool to manage git hooks and run code checks in an isolated, reproducible environment. I suggest we use this tool to manage code formatting, code linting, and static type checking. We can optionally allow developers to allow pre-commit to manage git hooks for the repository.

@kwigley kwigley added the tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality label Jul 15, 2021
@github-actions
Copy link
Contributor

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.

@github-actions github-actions bot added the stale Issues that have gone stale label Jan 12, 2022
@kwigley kwigley removed the stale Issues that have gone stale label Jan 12, 2022
@leahwicz leahwicz added the jira label Jan 27, 2022
@github-actions github-actions bot changed the title use pre-commit to manage code checks (enforce styleguide, code formatting, type checks) [CT-104] use pre-commit to manage code checks (enforce styleguide, code formatting, type checks) Jan 27, 2022
@iknox-fa
Copy link
Contributor

Awaiting clarification in slack:
https://dbt-labs.slack.com/archives/C02UT9M9613/p1643323532290579

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality
Projects
None yet
Development

No branches or pull requests

3 participants