fix(milestone-sync): suppress leaked API response bodies #5
No reviewers
Labels
No labels
Kind/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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
WulfScience-FOSS/ci-actions!5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/cleanup"
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?
Five api_patch call sites weren't redirecting or capturing their response,
so the raw JSON leaked directly into the job log (confirmed live when
milestone PATCH responses showed up jammed onto the same line as the
'→ milestone state=...' message). issue-sync.sh and issue-intake.sh
already handled this correctly — only milestone-sync.sh had the gap.