-
Notifications
You must be signed in to change notification settings - Fork 2
Prepare for and hold a second pyright/Ruff correction day [21st May] #8553
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
Comments
Might be good to briefly discuss at planning whether this needs to be another whole day, or we whether what remains isn't large enough to justify a full tech-debt style day. |
Friday is more important for this sprint, defer this to maybe January |
ISISComputingGroup/IBEX-device-generator#4 Open PR from previous pyright day |
What still needs doing. I am suggesting we make
genie_python
After this is done, the following core python repos need doing.
|
comment to make project board checks happier |
Uh oh!
There was an error while loading. Please reload this page.
Issue Description
As a developer working on IBEX I want to continue to clear out and correct the legacy pyright/ruff errors that are in the system now that we have instigated these checks as standard so that small/urgent changes don't lead to lots of fixing. This will follow on and add to the work started in #8527.
Acceptance Criteria
What is the acceptance criteria of this ticket? What should the reviewer expect to be complete?
How to Review
Before making a PR...
planning 69:00 2024/10/31
Time in recording of planning meeting: 00h12m 2024/11/28
Discussed planning 05/02/2025 00:30:30
The text was updated successfully, but these errors were encountered: