[no-ci] Mention mostly the ability to automatically update submodules

[seberg]

Expand docs slightly to mention that you can set up your clone to automatically keep submodules up to date.

@rwgk is this roughly what you are looking for?

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: NVIDIA/cuda-python/.coderabbit.yaml
• Review profile: CHILL
• Plan: Enterprise
• Run ID: 5d8fdfc1-2810-4d62-9b01-7536893430ce

📥 Commits

Reviewing files that changed from the base of the PR and between 31915ee and 0f5f25e.

📒 Files selected for processing: 1

• CONTRIBUTING.md

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.

📝 Summary

Summary by CodeRabbit

• Documentation
  • Updated cloning guidance to initialize submodules recursively and documented recursive submodule updates when pulling, checking out, or switching branches. Pushes do not update submodules recursively.
  • Added an “Updating your clone” section explaining how to initialize newly added submodules, and linked to it from the table of contents.

CONTRIBUTING.md now recommends recursive cloning and documents Git settings for submodule updates. It also explains how to pull updates and initialize newly added submodules.

Changes: Clone submodule updates

Layer / File(s)	Summary
Document submodule update methods CONTRIBUTING.md	The table of contents links to the update guidance. The cloning instructions describe recursive cloning, submodule recursion settings for pull, checkout, and switch, and disabling recursive pushes. The update guidance covers pulling and initializing newly added submodules.

Priority: ⬇️ Low

Change: Other

Merge Risk: ⚪ Minimal · up to 0f5f2

The submodule guidance covers recursive updates without unexpectedly recursing on pushes, and provides a general initialization step after updates. No material merge risk remains.

- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

✨ Finishing Touches: 💡 1

🛠️ Fix failing CI checks: 💡

• Commit to this branch
• Create a new PR

[coderabbitai]

Actionable comments posted: 2

---

ℹ️ Review info

⚙️ Run configuration

• Configuration used: Repository: NVIDIA/cuda-python/.coderabbit.yaml
• Review profile: CHILL
• Plan: Enterprise
• Run ID: 78a91f92-c74c-4dcc-9f43-4037f0a89fe7

📥 Commits

Reviewing files that changed from the base of the PR and between 1cd41ea and 31915ee.

📒 Files selected for processing: 1

• CONTRIBUTING.md

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.

[github-actions]

Doc Preview CI
🚀 View preview at https://nvidia.github.io/cuda-python/pr-preview/pr-3105/
https://nvidia.github.io/cuda-python/pr-preview/pr-3105/cuda-core/
https://nvidia.github.io/cuda-python/pr-preview/pr-3105/cuda-bindings/
https://nvidia.github.io/cuda-python/pr-preview/pr-3105/cuda-pathfinder/
Preview will be ready when the GitHub Pages deployment is complete.

[rwgk]

I went ahead and added a commit to simplify/polish the new sections. The changes take the coderabbit suggestions into account.

[rwgk]

Closing / re-opening to re-trigger GHA after adding [no-ci].