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

feat: Add pre-commit and apply fixes #677

Closed

Conversation

27Bslash6
Copy link

@27Bslash6 27Bslash6 commented Jun 15, 2022

No module or app logic changes are included in this PR, it's purely QA and tooling uplift, in preparation for a follow up solving issues with resource name lengths.

General QA uplift:

  • Forces standard line endings
  • Replacing tabs with spaces
  • Removing trailing whitespace
  • Makefile targets for QA shortcuts

Python QA:

  • sorts imports via isort
  • removes unused imports
  • remove yapf formatting in favour of black
  • applies code style fixes as suggested by flake8

Terraform QA:

  • applies terraform fmt
  • generates documentation

Future improvements: TF module linting via tflint

Ray Walker added 4 commits June 15, 2022 21:48
General QA uplift:
- Forces standard line endings
- Replacing tabs with spaces
- Removing trailing whitespace
- Makefile targets for QA shortcuts

 Python QA:
 - sorts imports via isort
 - applies formatting via black
 - applies code style fixes suggested by flake8

Terraform QA:
- applies terraform fmt
- generates documentation
Also bump actions/checkout to latest version
@google-cla
Copy link

google-cla bot commented Jun 15, 2022

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Copy link
Collaborator

@ludoo ludoo left a comment

Choose a reason for hiding this comment

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

Hey, thanks for this but we don't feel we should increase friction for developers at this moment in time. Having several tools needed before a Python PR can be sent seems like a large overhead.

@ludoo
Copy link
Collaborator

ludoo commented Jun 15, 2022

I am going to close this, feel free to resubmit PRs one at a time for each individual extra feature, and we can take it from there.

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.

2 participants