minor chore

[justanwar]

• Sync Flathub info with upstream
• minor documentation fixes

[coderabbitai]

Walkthrough

Documentation updates across two files: a Markdown link syntax correction in README.md (removing extraneous space) and a version number bump from 0.14.13.x to 0.14.15.x in README_windows.txt.

Changes

Cohort / File(s)	Summary
Markdown link syntax fix doc/README.md	Corrected hyperlink formatting in the Setup section by removing space between link text and URL parenthesis: [Firo Core] (URL) → [Firo Core](URL)
Version metadata update doc/README_windows.txt	Updated version string from "Firo Core 0.14.13.x" to "Firo Core 0.14.15.x"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

---

🐰 A hop and a skip through the docs we go,
One link fixed, one version to show,
Spaces removed, numbers updated bright,
Simple edits, oh what a delight!
Our Warren's changelog grows just right. ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is incomplete and does not follow the required template structure with the mandatory 'PR intention' section filled out properly.	Add a detailed 'PR intention' section explaining what changes were made and why, following the template format. Expand the bullet points into complete descriptions.
Title check	❓ Inconclusive	The title 'minor chore' is vague and generic, using non-descriptive language that doesn't convey meaningful information about the specific changes made.	Replace with a more specific title that describes the actual changes, such as 'Fix markdown link formatting and update version strings' or 'Update documentation: fix link syntax and version metadata'.

✅ Passed checks (1 passed)

Check name	Status	Explanation
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 chore

---

📜 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 0fb0139 and f1b3fe5.

⛔ Files ignored due to path filters (1)

• contrib/flathub/org.firo.firo-qt.metainfo.xml is excluded by !**/*.xml

📒 Files selected for processing (2)

• doc/README.md (1 hunks)
• doc/README_windows.txt (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (8)

• GitHub Check: build-guix-aarch64-linux-gnu
• GitHub Check: build-guix-x86_64-linux-gnu
• GitHub Check: build-guix-arm64-apple-darwin
• GitHub Check: build-guix-x86_64-w64-mingw32
• GitHub Check: build-guix-x86_64-apple-darwin
• GitHub Check: build-mac-cmake
• GitHub Check: build-linux-cmake
• GitHub Check: build-windows-cmake

🔇 Additional comments (2)

doc/README.md (1)

6-6: Markdown link syntax corrected.

The fix removes the stray space between the link text and URL, conforming to proper Markdown syntax. This ensures the hyperlink renders correctly across all Markdown parsers.

doc/README_windows.txt (1)

1-1: Version string updated to 0.14.15.x.

Documentation version metadata synchronized with upstream release. Change is straightforward and correct.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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.}

[aleflm]

Thanks.