Add liquidgo to Template Engines

[pierre-b]

Forge link: https://github.com/Notifuse/liquidgo
pkg.go.dev: https://pkg.go.dev/github.com/Notifuse/liquidgo
goreportcard.com: https://goreportcard.com/report/github.com/Notifuse/liquidgo
Coverage: https://codecov.io/github/notifuse/liquidgo

Summary by CodeRabbit

• Documentation
  • Added a new template engine to the list of supported options in the documentation.

[coderabbitai]

Walkthrough

A new template engine entry "liquidgo" with its corresponding URL is added to the Template Engines section of the README.md file, expanding the list of supported template engines without removing or modifying any existing entries.

Changes

Cohort / File(s)	Summary
Documentation Updates README.md	Added new template engine entry "liquidgo" to Template Engines section with its URL

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Straightforward documentation addition with no logic changes
• Single line addition in a documentation list

Poem

🐰 A liquid engine, shiny and new,
Flows into the README with templates so true,
One line added, the list grows wide,
More tools for builders to run with pride! ✨

Pre-merge checks and finishing touches

✅ 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 and concisely describes the main change: adding liquidgo to the Template Engines section of the README.
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

---

📜 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 2698e59 and 1b4eac5.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (3)

README.md

📄 CodeRabbit inference engine (AGENTS.md)

README.md: When modifying the Awesome list, keep categories with at least three entries
Descriptions in the Awesome list must end with a period
Avoid promotional copy; keep descriptions concise and neutral in the Awesome list
Do not remove existing list content unless removal is requested and justified

Files:

• README.md

**/*.md

📄 CodeRabbit inference engine (AGENTS.md)

Keep documentation in English

Files:

• README.md

{README.md,COVERAGE.md}

📄 CodeRabbit inference engine (AGENTS.md)

Align rendered documentation (README.md, COVERAGE.md, etc.) with behavior changes in main.go or helper packages

Files:

• README.md

⏰ 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). (2)

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: quality

🔇 Additional comments (1)

README.md (1)

2411-2412: Addition complies with Awesome-Go rules.

Entry is concise, ends with a period, non‑promotional, and alphabetically placed after “liquid.” Looks good.

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

[github-actions]

Automated Quality Checks (from CONTRIBUTING minimum standards)

• Repo: OK
• pkg.go.dev: OK
• goreportcard: OK (grade unknown)
• coverage: OK

These checks are a best-effort automation and do not replace human review.