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

chore: Add pylint GitHub Action #4107

Merged
merged 11 commits into from
Sep 26, 2023
Merged

chore: Add pylint GitHub Action #4107

merged 11 commits into from
Sep 26, 2023

Conversation

liuverta
Copy link
Contributor

@liuverta liuverta commented Sep 26, 2023

Impact and Context

Run pylint as a GitHub action when a PR contains changes to the client codebase (not including the test suite—we don't lint that today)

Risks and Area of Effect

  • Is this a breaking change?

Testing

  • Unit test
  • Deployed to dev env
  • Other (explain)

Screenshot 2023-09-26 at 9 21 20 AM

Reverting

  • Contains Migration - Do Not Revert

Revert this PR.

@github-actions
Copy link

Common Code Coverage

Overall Project 15.01% 🍏

There is no coverage information present for the Files changed

@github-actions
Copy link

github-actions bot commented Sep 26, 2023

Backend Code Coverage

Overall Project 61.32% 🍏

There is no coverage information present for the Files changed

@liuverta liuverta merged commit c2ec413 into main Sep 26, 2023
1 check passed
@liuverta liuverta deleted the liu/pylint branch September 26, 2023 17:33
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.

1 participant