Skip to content

Conversation

benjaminye
Copy link
Contributor

Addresses #103 and partially #106

New Github Action

  • Added Github action to Lint and Format using ruff
  • Added configs for ruff
  • Automatically commit code changes onto PR

Lint and Format

  • Linted and Formatted codebase (minus scripts within llama2 and mistral)

Request for Comment

@truskovskiyk

  • Right now it's set up to automatically commit changes lint and formatting fixes directly onto the PR.
  • Is this alright?
  • This requires read/write access for github workflow runners under repo settings

@benjaminye benjaminye added the enhancement New feature or request label Apr 2, 2024
@benjaminye benjaminye self-assigned this Apr 2, 2024
Copy link
Contributor

@truskovskiyk truskovskiyk left a comment

Choose a reason for hiding this comment

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

thanks, much nicer!

README.md Outdated
Comment on lines 259 to 264
### Checklist Before Pull Request (Optional)

1. Use `ruff check` to check for lint errors
2. Use `ruff format` to apply formatting

NOTE: Ruff linting and formatting are done automatically when PR is raised using Git Action (and changes will be automatically applied via another commit). It is, however, a good practice to check and fix lint errors, as well as apply formatting before PR.
Copy link
Contributor

Choose a reason for hiding this comment

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

might be nice to add this into Makefile after

@truskovskiyk
Copy link
Contributor

@benjaminye

Right now it's set up to automatically commit changes lint and formatting fixes directly onto the PR.
Is this alright?

No, give access CI to write code into main branch is not best idea, let's just keep check-in CI - if code does not follow style - PR fails. but this exact fix - need to be done by author of PR

@benjaminye
Copy link
Contributor Author

@benjaminye

Right now it's set up to automatically commit changes lint and formatting fixes directly onto the PR.
Is this alright?

No, give access CI to write code into main branch is not best idea, let's just keep check-in CI - if code does not follow style - PR fails. but this exact fix - need to be done by author of PR

@truskovskiyk
Amended desired changes, as required. See 36688e0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
2 participants