Fluid analyze

[Mainbird]

Summary by CodeRabbit

• New Features

  • Added automated linting for Fluid template files in the CI/CD pipeline.

• Documentation

  • Updated documentation to reflect the new analysis template inclusion.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a9e40dd6-46f1-4799-a3d7-31be1800b9c7

📥 Commits

Reviewing files that changed from the base of the PR and between ee4bbe0 and 7939c48.

📒 Files selected for processing (3)

• .gitlab-ci.yml.dist
• README.md
• analyze/analyze-fluid-lint.yaml

---

📝 Walkthrough

Walkthrough

A new GitLab CI job for linting Fluid template files is introduced via a new template file analyze/analyze-fluid-lint.yaml, which is registered in .gitlab-ci.yml.dist and documented in README.md.

Changes

Cohort / File(s)	Summary
Pipeline Configuration .gitlab-ci.yml.dist, README.md	Added include entry for the new Fluid linting template; updated documentation to reference the new analysis template.
Fluid Lint CI Job analyze/analyze-fluid-lint.yaml	New GitLab CI job analyze:fluid:lint that runs Composer linting for Fluid templates in the analyze stage, with conditional execution rules based on pipeline source, commit tags, and file changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• feat: add linting jobs for JavaScript and CSS/SCSS in CI configuration #14 — Adds JS and style lint CI jobs in a similar pattern, establishing consistency across analyze-stage linting templates.

Suggested reviewers

• konradmichalik

Poem

🐰 A fluid linter hops into the fold,
Checking templates with rules so bold,
Composer runs swift through the CI night,
Liquid syntax shines crystal bright! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Fluid analyze' is vague and generic, lacking specificity about what analysis is being added or configured.	Use a more descriptive title like 'Add Fluid linting CI job' or 'Add analyze-fluid-lint CI template' to clearly convey the main change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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
• Commit unit tests in branch fluid-analyze

---

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