Skip to content

[canary] trigger ruff E501 for Phalanx CI-Fixer test #1

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.

Sign up for GitHub

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

Open
rnagulapalle wants to merge 2 commits into
base: main
Choose a base branch
from
Open

[canary] trigger ruff E501 for Phalanx CI-Fixer test #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
02032df
canary: trigger ruff E501 via long comment (Phalanx CI-Fixer test)
rnagulapalle Apr 23, 2026
24e2fc0
ci: re-trigger after workflow enable
rnagulapalle Apr 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions src/humanize/filesize.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
"""Bits and bytes related humanization."""
# canary: this comment intentionally exceeds the 88-character ruff default to trigger E501 on the lint workflow

Check failure on line 2 in src/humanize/filesize.py

View workflow job for this annotation

GitHub Actions / lint

ruff (E501) 

src/humanize/filesize.py:2:89: E501 Line too long (111 > 88)

Check failure on line 2 in src/humanize/filesize.py

View workflow job for this annotation

GitHub Actions / lint

ruff (E501) 

src/humanize/filesize.py:2:89: E501 Line too long (111 > 88)

from __future__ import annotations

Expand Down
Loading