mention difference between latest and main

[EvilOlaf]

Do a PR so drunk rabbit can complain about stuff.

Fixes #12

Summary by CodeRabbit

• Documentation
  • Added guidance explaining which Docker image tags to use: images tagged "latest" are tested and recommended for stable use, while other tags represent active development or untested builds. The new notes help users choose the appropriate image for production or experimentation.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

README.md updated with a new subsection "Which Docker image? main or latest?" clarifying that images tagged latest are tested and known to work, while other tags (including main) are active development/untested builds.

Changes

Cohort / File(s)	Change Summary
Docker Documentation README.md	Added new subsection "Which Docker image? main or latest?" explaining that the latest tag is tested and reliable, whereas other tags (e.g., main) are untested auto-builds and may break.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single-file documentation addition; no code or behavior changes.
• Files to check:
  • README.md — verify wording and placement of the new subsection.

Poem

🐰 I hopped through docs to leave a light trace,
"Latest" is steady, a safe, tested place,
Main is for builders still finding their tune,
Try not to trip on an untested rune,
Happy docking — I’ll nibble a carrot of grace.

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: adding documentation about the difference between latest and main Docker image tags.
Linked Issues check	✅ Passed	The PR addresses both objectives from issue #12: clarifying that latest images are tested and that main images are untested auto-builds.
Out of Scope Changes check	✅ Passed	The change is limited to README.md documentation about Docker image tags, which directly aligns with the linked issue requirements.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch EvilOlaf-patch-1

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 49f704a and ec2ae63.

📒 Files selected for processing (1)

• README.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

58-63: Consider clarifying which branch main represents and improving documentation tone.

The new section addresses the PR objective to mention the difference between latest and main, but could be improved in two ways:

1. Specificity: The content treats main as one of many "untested builds" without explicitly identifying it as the development/main branch. Clarifying that main represents the active development branch would make the distinction from latest (the stable release tag) clearer.

2. Tone: The sarcastic phrasing ("don't complain about breakage", "I tend to break things randomly. You have been warned.") may undermine user confidence in the documentation. Consider a more straightforward warning tone that still conveys the message without the sarcasm.

Here's a suggested revision:

 ### Which Docker image? `main` or `latest`?
 
 Images tagged as `latest` are **tested and known to work.**
 
-**Any** other are automated untested builds. Do not use...or do but don't complain about breakage.   
-I tend to break things randomly. You have been warned.
+The `main` tag represents the active development branch with untested builds. Other tags are also untested and may contain breaking changes or instability.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 58f3480 and 49f704a.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📚 Learning: 2025-11-26T08:22:42.118Z

Learnt from: EvilOlaf
Repo: EvilOlaf/scum PR: 8
File: README.md:53-56
Timestamp: 2025-11-26T08:22:42.118Z
Learning: In the EvilOlaf/scum repository, providing detailed help with customizing the gaming experience (such as extensive SCUM server configuration guidance) is out of scope. The repository focuses on the Docker container setup rather than comprehensive game server customization documentation.

Applied to files:

• README.md

📚 Learning: 2025-11-26T08:20:53.013Z

Learnt from: EvilOlaf
Repo: EvilOlaf/scum PR: 8
File: README.md:53-56
Timestamp: 2025-11-26T08:20:53.013Z
Learning: The URL https://scum.wiki.gg/wiki/Dedicated_Server_Setup is empty and should not be suggested for SCUM server configuration documentation. The working alternative is https://scum.fandom.com/wiki/Server_Settings for server settings information.

Applied to files:

• README.md