MetOffice / MetOffice/fab

Apply ruff formatting to the codebase

Open
#489 6 comments 1 reaction 1 assignee Claimed by @t00sa View on GitHub
Release technical debt
Dominant language
Python
Stars
9
Forks
9
Avg merge
12d 12h
Merged PRs (30d)
2

Description

@yaswant is proposing that we standardise on ruff as our linter and formatter. Testing shows that fab already complies with the linter, but changes are required to update the formatting. To minimise the impact of the change, we should:

- [ ] reformat the codebase immediately before the next release
- [ ] create a `.git-blame-ignore-revs` in the root of the repository and add the commit hash of the reformatting release, to ensure that `git blame` is continues to work as expected
- [ ] update the workflow to apply ruff as a both a linter and format checker

I suggest we adhere to the ruff/black default line length [as justified in the black documentation](https://black.readthedocs.io/en/stable/the_black_code_style/current_style.html#line-length).

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.