Added version control section to Must see

[sasham1]

Why do you think the link is worth adding on this list?

Version control is something every game project ends up needing, and the list didn't have a section for it yet. Handling large binary assets is painful with vanilla Git, and there's a whole category of version control tools game devs use - figured it'd be useful to group them in one place.

Does this project has any License?
Mixed - Git LFS (MIT) and Subversion (Apache 2.0) are open source, the rest are commercial with free tiers

Summary by CodeRabbit

• Documentation
  • Added a new “Version Control” section with curated tool resources: Diversion, Git LFS, Helix Core (Perforce), Subversion, and Unity Version Control.
  • Updated the Table of Contents to include and link to the new “Version Control” section for easier navigation.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: bad980ee-6943-487b-b33c-bea33bf39095

📥 Commits

Reviewing files that changed from the base of the PR and between 88e0be4 and 613934f.

📒 Files selected for processing (1)

• README.md

✅ Files skipped from review due to trivial changes (1)

• README.md

---

📝 Walkthrough

Walkthrough

Added a new "Version Control" section to README.md with five curated tool links (Diversion, Git LFS, Helix Core/Perforce, Subversion, Unity Version Control) and updated the Table of Contents to include a Version Control entry linking to that section.

Changes

Version Control docs add

Layer / File(s)	Summary
Version Control section and TOC update README.md	Inserted Version Control entry in the Table of Contents linking to #version-control, and added the corresponding ### Version Control section with links to Diversion, Git LFS, Helix Core (Perforce), Subversion, and Unity Version Control.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A small new branch sprouts in the readme land,
Five version tools held in a careful hand,
Links hop in order, tidy and bright,
Rabbity cheers for clarity tonight! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title is vague and incomplete—'Must see' is unclear as to what the section is about, and the title doesn't fully convey that the section is specifically about version control tools for game development.	Consider a more descriptive title like 'Add version control tools section to documentation' to clearly communicate the primary change.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

🧹 Nitpick comments (1)

README.md (1)

512-512: Optional wording polish: use “formerly known as”.

Line 512 reads fine, but “formerly known as Plastic SCM” is a bit tighter stylistically.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 512, Replace the phrase "Previously known as Plastic SCM"
with the tighter wording "formerly known as Plastic SCM" in the README entry for
"Unity Version Control" (the line containing ":money_with_wings: [Unity Version
Control] ... Previously known as Plastic SCM") so the entry reads with "formerly
known as Plastic SCM" instead.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@README.md`:
- Line 512: Replace the phrase "Previously known as Plastic SCM" with the
tighter wording "formerly known as Plastic SCM" in the README entry for "Unity
Version Control" (the line containing ":money_with_wings: [Unity Version
Control] ... Previously known as Plastic SCM") so the entry reads with "formerly
known as Plastic SCM" instead.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6b6b9026-4a80-4e4b-8720-6dd1917e6e57

📥 Commits

Reviewing files that changed from the base of the PR and between 04627f4 and 14ce10a.

📒 Files selected for processing (1)

• README.md

[sasham1]

Fixed wording as suggested by CodeRabbit