FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

docs: update README with examples and remove outdated sections by Miou-zora · Pull Request #482 · EngineSquared/EngineSquared · GitHub

docs: update README with examples and remove outdated sections - #482

Merged
Miou-zora merged 2 commits into
mainfrom
add-examples-to-readme
Mar 14, 2026
Merged

docs: update README with examples and remove outdated sections#482
Miou-zora merged 2 commits into
mainfrom
add-examples-to-readme

Conversation

Miou-zora commented Mar 14, 2026
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Contributor

Pull Request

Description

Update the README to be up to date

Related Issues

None

Type of Change

Please delete options that are not relevant.

  • Documentation update

Changes Made

  • Updated dependencies
  • Added images and examples
  • Remove deprecated doc

Documentation

  • I have updated the relevant documentation

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published

Breaking Changes

None

Additional Notes

None

Summary by CodeRabbit

  • Documentation
    • Updated project description to "Open-source game engine" and removed project-specific tagline
    • Added an Examples section with images and links
    • Replaced local build/setup and coding-style instructions with a Documentation section pointing to the online wiki
    • Removed developer environment requirements (Vulkan SDK, Visual Studio) and streamlined requirements list
    • Minor formatting and structural cleanups

coderabbitai Bot commented Mar 14, 2026
edited
Loading

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

The README.md was reworked: the project description was simplified, development setup and coding style sections were removed, documentation links now point to the online wiki, Vulkan/Visual Studio requirements were removed, and an Examples section was added.

Changes

Cohort / File(s) Summary
Documentation / README
README.md
Simplified project description, removed development environment setup and coding style sections, removed local Doxygen/build docs steps, removed Vulkan SDK and Visual Studio requirements, added an Examples section, and redirected documentation to the online wiki.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 A rabbit peeks at lighter readmes bright,
Gone are heavy guides that kept us up at night.
The wiki basks, examples in a row,
Shorter hops and clearer trails to go. ✨

🚥 Pre-merge checks | ✅ 3 ✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: updating the README with examples and removing outdated sections, which aligns with the file summary and PR objectives.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches 🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch add-examples-to-readme
📝 Coding Plan
  • Generate coding plan for human review comments

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

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

Tip

CodeRabbit can use Clang for C/C++ static analysis and code quality checks.

Clang provides comprehensive static analysis for C and C++ code, including syntax checking, type checking, and various warning diagnostics.

coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Line 1: The README images lack alt text which breaks accessibility and
linting; update each <img> tag (e.g., the one referencing
"docs/images/Banner.png" and the other images around the example section) to
include meaningful alt attributes (for example alt="Project banner" for the
banner and descriptive alt text for the example images) so every <img> tag has
an appropriate alt="" value.
- Around line 10-11: Update the README wording: hyphenate "developer-friendly"
in the first sentence and revise the second sentence to read naturally — replace
"provide truly open-source project and be accessible to everyone" with something
like "be a truly open-source project and be accessible to everyone" or "be a
truly open-source project and accessible to everyone" so the article and
parallel structure are correct; modify the lines containing "developer friendly"
and "truly open-source project" accordingly.
- Line 17: Replace the invalid HTML break tag "</br>" with a valid self-closing
break tag (either "<br />" or "<br>") in the README image lines where the markup
shows the image tag and trailing break; search for the literal string "</br>"
and update those occurrences so the Markdown renders correctly (e.g., change
"</br>" to "<br />").

ℹ️ Review info ⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a68a0af7-7ab7-4311-81bf-741d4de7c82d

📥 Commits

Reviewing files that changed from the base of the PR and between d97b893 and ebc64b1.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
Comment thread README.md Outdated
Comment thread README.md Outdated

coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality
♻️ Duplicate comments (2)
README.md (2)

1-1: ⚠️ Potential issue | 🟡 Minor

Add alt text to the banner image (accessibility/lint).

Line 1 still uses an <img> without alt, which triggers MD045 and reduces accessibility.

Suggested fix
-<img src="docs/images/Banner.png">
+<img src="docs/images/Banner.png" alt="Engine² banner">
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 1, The README uses an <img> tag referencing Banner.png
without an alt attribute which triggers MD045; update the <img
src="docs/images/Banner.png"> element to include a meaningful alt attribute (for
example alt="Project banner" or a short descriptive phrase) so the tag becomes
<img src="docs/images/Banner.png" alt="..."> to satisfy accessibility/lint
rules.

11-11: ⚠️ Potential issue | 🟡 Minor

Fix grammar in project description sentence.

Line 11 reads unnaturally (“provide truly open-source project”). Suggested wording:

Suggested fix
-It is designed to provide truly open-source project and be accessible to everyone.
+It is designed to be a truly open-source project and be accessible to everyone.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 11, Replace the awkward sentence "It is designed to
provide truly open-source project and be accessible to everyone." with a
grammatically correct version such as "It is designed to be a truly open-source
project and to be accessible to everyone." Locate the exact sentence in
README.md and update it accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@README.md`:
- Line 1: The README uses an <img> tag referencing Banner.png without an alt
attribute which triggers MD045; update the <img src="docs/images/Banner.png">
element to include a meaningful alt attribute (for example alt="Project banner"
or a short descriptive phrase) so the tag becomes <img
src="docs/images/Banner.png" alt="..."> to satisfy accessibility/lint rules.
- Line 11: Replace the awkward sentence "It is designed to provide truly
open-source project and be accessible to everyone." with a grammatically correct
version such as "It is designed to be a truly open-source project and to be
accessible to everyone." Locate the exact sentence in README.md and update it
accordingly.

ℹ️ Review info ⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 74225687-379a-4c1d-80f6-d93da566d36e

📥 Commits

Reviewing files that changed from the base of the PR and between ebc64b1 and 5dea632.

📒 Files selected for processing (1)
  • README.md

Copy link
Copy Markdown

Miou-zora merged commit 2fe6afb into main Mar 14, 2026
21 of 22 checks passed
Miou-zora deleted the add-examples-to-readme branch March 14, 2026 18:41
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant


Back | FazBrowse Home | New Git URL