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

Introduce Linting #31

Merged
merged 19 commits into from
Apr 22, 2024
Merged

Introduce Linting #31

merged 19 commits into from
Apr 22, 2024

Conversation

judtinzhang
Copy link
Member

@judtinzhang judtinzhang commented Apr 16, 2024

  • black, isort, flake8 dependency upgrades
  • Linted files
  • Added pre-commit
  • Add coverage (thought not used at the moment)
  • With this PR, highly suggest setting up pre-commit

@judtinzhang judtinzhang linked an issue Apr 16, 2024 that may be closed by this pull request
Copy link
Member

@jeofo jeofo left a comment

Choose a reason for hiding this comment

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

LGTM 🥶


[dev-packages]
isort = "*"
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a reason we don't need isort anymore?

Copy link

gitguardian bot commented Apr 16, 2024

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
9451515 Triggered Generic Password c97d387 .github/workflows/build-deploy.yaml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

setup.cfg Outdated

[isort]
default_section = THIRDPARTY
known_first_party = pennmobile, dining, gsr_booking, user, laundry
Copy link

Choose a reason for hiding this comment

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

we should change these right

@@ -53,7 +55,7 @@ def make_request():

def run_threads():
with ThreadPoolExecutor(max_workers=THREADS) as executor:
futures = [executor.submit(make_request) for _ in range(NUMBER_OF_REQUESTS)]
_ = [executor.submit(make_request) for _ in range(NUMBER_OF_REQUESTS)]
Copy link

Choose a reason for hiding this comment

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

lol why not 2 lines, this seems wasteful

@judtinzhang judtinzhang merged commit 9cdd458 into master Apr 22, 2024
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Add Linting to Analytics
4 participants