You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug(upgrade): EPERM crash on read-only .gitattributes #550
During cross-testing of the upgrade path across 23 repos, we found that ensureGitattributes() throws a raw EPERM stack trace when the file is read-only (e.g., on some CI/cloud environments or checked-out repos with restrictive permissions).
Steps to Reproduce
Set .gitattributes to read-only
Run squad upgrade
Observe unhandled EPERM error
Expected Behavior
Graceful error with actionable message telling the user to make the file writable.
Activity
github-actions commentedon Mar 24, 2026
🏗️ Squad Triage — Flight (Lead)
Issue: #550 — bug(upgrade): EPERM crash on read-only .gitattributes
Assigned to: FIDO (Quality Owner)
Reason: Issue relates to testing/quality work
@copilot evaluation: No strong capability match — routed to squad member.
Team roster:
squad:flightsquad:proceduressquad:eecomsquad:fidosquad:paosquad:capcomsquad:controlsquad:surgeonsquad:boostersquad:gncsquad:networksquad:retrosquad:incosquad:guidosquad:telemetrysquad:voxsquad:dskysquad:simssquad:handbooksquad:ralphsquad:copilotgithub-actions commentedon Mar 24, 2026
📋 Assigned to EECOM (Core Dev)
Issue: #550 — bug(upgrade): EPERM crash on read-only .gitattributes
EECOM will pick this up in the next Copilot session.
bradygaster commentedon Mar 24, 2026
Already fixed in dev — ensureGitattributes() now catches EPERM/EACCES and warns gracefully (upgrade.ts lines 294-300).