dprint check walks untracked .build-backup-* directories under apps/desktop/native
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 94/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- developer-experience, tooling
Research direction
Update the repository ignore or dprint exclude configuration so backup directories under apps/desktop/native/.build-* are skipped. Start by inspecting .gitignore and the dprint configuration, then reproduce with bun run ci or the relevant dprint check. The change is done when an existing .build-backup-* directory no longer produces files in the check.
Written by the indexing model from the issue text.
Description
.gitignore ignores apps/desktop/native/.build/ but not recovery copies such as apps/desktop/native/.build-backup-20261006-210348/. With one present, bun run ci ran dprint check over it and failed on 406 third-party and generated files, with a very large diff (seen during githubnext/ace2#210).
bun run lint no longer has this problem, since oxlint now gets only git ls-files. dprint still walks every file that isn't ignored.
Fix: add apps/desktop/native/.build-*/ to .gitignore, or **/.build-backup-* to dprint's excludes. Moving a .build aside is no longer the recovery step, because the Desktop Tools build restores a drifted checkout itself. Old backups can still be lying around, though.
Moved from githubnext/desktop-tools#7.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/ace2
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
githubnext/ace2#486 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
githubnext/ace2#459 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/ace2#437 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
githubnext/ace2#442 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 40/100
githubnext/ace2#440 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Koenkk/zigbee-herdsman-converters#13540 ·
Maintainers usually reply within 1 day
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
iptv-org/iptv#55821 · 1 comment ·
Maintainers usually reply within 1 day
-
area/busola/ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
kyma-project/busola#5442 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/wterm#246 ·
Maintainers usually reply within 1 day