Fix link to sublime.xaml in theme creation guide

[Jaysum57]

No description provided.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated Markdown formatting in the documentation file by converting a standalone link reference to an inline link format, replacing the separate reference definition with embedded link syntax.

Changes

Cohort / File(s)	Change Summary
Documentation formatting how-to-create-a-theme.md	Converted standalone link reference [sublime.xaml] to inline link format [here](...) in the Overview section and removed the separate reference definition.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

This is a straightforward documentation formatting change affecting a single file with no functional implications.

Suggested labels

bug

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: converting a link reference format to an inline link in the theme creation documentation.
Description check	✅ Passed	No description was provided by the author; the check is lenient and passes as long as description is not completely off-topic.
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

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

how-to-create-a-theme.md (1)

3-3: Use descriptive link text for better accessibility and UX.

The link text "here" is not descriptive. For documentation, screen readers and users benefit from knowing what they're downloading before clicking. Consider using link text that references the file name or action directly.

Apply this diff to improve the link:

-If you make a theme for the first time, refer to the existing theme. Copy the **sublime.xaml** (This is one of the basic theme files.) in the theme folder of Flow and make it a new file.  Or you can download it [here](https://github.com/Flow-Launcher/Flow.Launcher/blob/dev/Flow.Launcher/Themes/Sublime.xaml).
+If you make a theme for the first time, refer to the existing theme. Copy the **sublime.xaml** (This is one of the basic theme files.) in the theme folder of Flow and make it a new file.  Or you can download [Sublime.xaml](https://github.com/Flow-Launcher/Flow.Launcher/blob/dev/Flow.Launcher/Themes/Sublime.xaml).

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cc8da14 and 008b2f9.

📒 Files selected for processing (1)

• how-to-create-a-theme.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

how-to-create-a-theme.md

3-3: Link text should be descriptive

(MD059, descriptive-link-text)