fix: mask token in ForgejoConfig __repr__ #166
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
thwap/hottea!166
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/132-config-token-leak"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds custom
__repr__toForgejoConfigthat shows only the first 4 characters of the token (e.g.,my-s****). Prevents accidental token leakage in logs or tracebacks.Closes #132
Audit Review — PR #166
Clean fix for #132 (Priority/High). Custom
__repr__onForgejoConfigmasks token (first 4 chars +****). Tests confirm token not leaked and empty token handled gracefully.No suggestions.
Summary
Result: COMMENT — no issues found.
APPROVED. Token properly masked, closes #132. Merge when ready.
4fdc257e2083f02a2c0f