Restore variables with noqa: F841 per review feedback#210
Merged
Conversation
Co-authored-by: rajeee <[email protected]>
Copilot
AI
changed the title
[WIP] Apply ruff lint fixes across codebase
Restore variables with noqa: F841 per review feedback
Feb 3, 2026
rajeee
approved these changes
Feb 3, 2026
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
Restores three intentionally unused variables that were removed during lint cleanup, adding
# noqa: F841suppressions as requested in code review.Changes
ochre/utils/envelope.py: Restoredbuilding_heightandbuilding_height_ftvariables with noqa commentsochre/utils/equipment.py: Restoredground_tempvariable with noqa commenttest/test_equipment/test_battery.py: Restoredinitial_capacityvariable with noqa commentAll variables are marked with
# noqa: F841to suppress unused variable warnings while preserving them for potential future use or dynamic access patterns.Checklist
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.