fix(misc): format must exclude ignored patterns

[pongells]

nx format commands will now correctly ignore
patterns defined in .gitignore or .nxignore

Current Behavior

The nx format commands (write, check) do not take into account ignored patterns.

Expected Behavior

The nx format commands (write, check) should not parse ignored patterns.

Related Issue(s)

#18568

Fixes #18568

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 21, 2023 1:16pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit f6bf833. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 8 targets

• linux nx affected --target=e2e --base=2638bb0db2839051c7b661a56199dccf5ee96086 --head=f6bf833ddddfd2ebafe0e758d7e50faaedc72cce --parallel=1
• linux nx affected --target=build --base=2638bb0db2839051c7b661a56199dccf5ee96086 --head=f6bf833ddddfd2ebafe0e758d7e50faaedc72cce --parallel=3
• linux nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• linux nx affected --target=lint --base=2638bb0db2839051c7b661a56199dccf5ee96086 --head=f6bf833ddddfd2ebafe0e758d7e50faaedc72cce --parallel=3
• linux nx affected --target=test --base=2638bb0db2839051c7b661a56199dccf5ee96086 --head=f6bf833ddddfd2ebafe0e758d7e50faaedc72cce --parallel=1
• nx-cloud record -- nx format:check --base=2638bb0db2839051c7b661a56199dccf5ee96086 --head=f6bf833ddddfd2ebafe0e758d7e50faaedc72cce
• linux nx documentation --no-dte
• macos nx affected -t e2e-macos --parallel=1 --base=2638bb0db2839051c7b661a56199dccf5ee96086 --head=f6bf833ddddfd2ebafe0e758d7e50faaedc72cce

---

Sent with 💌 from NxCloud.

[pongells]

@Cammisuli is there something missing?

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.