Add automated style/linting checks with Ruff

[RupeshMangalam21]

Pull Request

Description

Added GitHub Actions workflow for automated code style and linting checks using Ruff.

This PR implements automated style/linting checks which was requested in #28. The implementation includes:

• Added a new GitHub Actions workflow that runs Ruff checks with proper GitHub output formatting
• Updated the existing ruff.toml configuration to use the newer recommended structure with [lint] section
• Fixed deprecation warnings in the configuration
• Runs automated checks on all pushes
• Helps maintain consistent code quality across contributions

Main changes:

1. Added .github/workflows/lint.yml:
   • Uses Python 3.11 and latest GitHub Actions
   • Configured for both linting and formatting checks
   • Set up for automatic inline annotations in PRs
2. Updated ruff.toml:
   • Moved linting settings under proper [lint] section
   • Removed deprecated configurations
   • Added GitHub-specific output formatting
   • Maintained existing rules and exclusions

Fixes #28

How Has This Been Tested?

• Yes
• Tested the workflow locally using ruff check . and ruff format --check .
• Verified the GitHub Actions configuration using act
• Confirmed all deprecation warnings are resolved
• Tested with sample code changes to ensure linting rules are properly enforced

If your changes affect data processing, have you plotted any changes? i.e. have you done a quick sanity check?

• Yes
  (Not applicable as this change only affects development tooling)

Checklist:

• My code follows OCF's coding style guidelines
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation (workflow and configuration files are self-documenting)
• I have added tests that prove my fix is effective or that my feature works (workflow will test itself when merged)
• I have checked my code and corrected any misspellings

[RupeshMangalam21]

Hi, @peterdudfield @Sukh-P After Implementing the linting check, we have encountered several linting errors across the repository. Shall i create new issues to resolve them categorically?

[peterdudfield]

Thanks @RupeshMangalam21

My vote would be to

1. Merge this
2. create a separate issue to fix linting

@Sukh-P @dfulu you happy with adding this style of linting?

[RupeshMangalam21]

@peterdudfield Are we okay to merge this? I will create a new issue to resolve linting after merging.

[peterdudfield]

Thanks for this, im just asking the team about this, as it will effect a few things.
Ill let @Sukh-P @AUdaltsova and @dfulu comment

[Sukh-P]

This LGTM, sounds like a good plan to raise a PR after this to apply the linting to the codebase