Repository navigation
fix(repo): remove Windows case-conflicting DESIGN duplicate - #6140
diegosouzapw merged 2 commits into
Conversation
release/v3.8.44 tracks both DESIGN.md and design.md. On Windows, Git cannot materialize both paths separately, so DESIGN.md appears permanently modified after checkout/pull. Keep design.md because it contains the updated design-system rollout notes, and remove the stale uppercase duplicate created by the DESING.md rename.
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
@diegosouzapw I believe this should be addressed as a high priority. This bug makes development on Windows impossible. I request that you merge this ASAP. |
…ve-stale-design-md
|
Merged — thank you, @backryun! 🙏 And apologies — this cleans up a regression I introduced: in #6097 I renamed a stale |
d3edbb5
into
cheaper-inference:release/v3.8.44
…inference#6140) Remove stale root DESIGN.md (Windows case-conflict with design.md). Integrated into release/v3.8.44.
Summary
DESIGN.mdso the repository no longer tracks bothDESIGN.mdanddesign.md.design.md, which contains the current design-system rollout notes and is referenced by the design-grid guard.DESIGN.mdanddesign.mdas separate files, soDESIGN.mdcan appear permanently modified after checkout or pull.Related Issues
Validation
npm run lintnpm run test:unitnpm run test:coverage>= 60%for statements, lines, functions, and branchesnpm run check:docs-syncgit ls-filesgit diff --check upstream/release/v3.8.44..HEADcheck:any-budget:t11,check:tracked-artifactsTests Added Or Updated
Coverage Notes
src/,open-sse/,electron/, orbin/, so coverage is not affected.Reviewer Notes
DESIGN.mdis the stale duplicate introduced by theDESING.md => DESIGN.mdrename.design.mdis the current document lineage from the dashboard visual identity work and should remain the tracked design document.