Open
Conversation
- Added 'backend-lint.yml' for automated python style and syntax checks
using github actions
- Uses Black for code formatting
- Uses Flake8 for syntax checks
Owner
|
@drhhhh I will review this code. |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Before it would only run when a change is made in the backend folder. Now it will run on all pushes to the repo.
Reformatted all Python files in the backend directory using Black to ensure consistent code style.
changes made to backend linting workflow
Owner
|
@drhhhh This is good, I will review your formatting changes, write a review, and merged the code later. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Type of Change
How to Test Changes
Ensure that the linting for Python works and shows up when a PR is made.
Checklist/Sanity Checking