chore: address FromAsCasing warning

[ma-04]

Summary by CodeRabbit

• Style
  • Standardized capitalization of stage aliases in the Docker build configuration to improve readability and align with common conventions. This is a cosmetic change only—no impact on images produced, build performance, or application behavior. No configuration updates or user actions are required; existing workflows continue to work as before. No user-facing changes.

[coderabbitai]

Walkthrough

Changed the Dockerfile stage alias keyword from "as" to "AS" in three FROM statements (composer_builder, wpcli_builder, builder). No modifications to build steps, dependencies, or functionality.

Changes

Cohort / File(s)	Summary of Changes
Dockerfile capitalization php/Dockerfile	Uppercased stage alias keyword: FROM ... as → FROM ... AS for composer_builder, wpcli_builder, and builder; no functional changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

In the dock where layers pass,
I nibble logs and sip my grass—
lowercase gone, now uppercase AS,
stages line up, crisp as glass.
Thump of joy, no breaking mass—
hop along, build shall smoothly class! 🐇🚢

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 PR title "chore: address FromAsCasing warning" is concise, uses a conventional commit prefix, and accurately describes the primary change (fixing FROM/AS casing in Dockerfiles to resolve a lint warning), so it reflects the changeset clearly.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• 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 2e5e00f and e33dc44.

📒 Files selected for processing (1)

• php/Dockerfile (2 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). (9)

• GitHub Check: build-php (8.0)
• GitHub Check: build-php (8.1)
• GitHub Check: build-php (7.4)
• GitHub Check: build-php (8.2)
• GitHub Check: build-php (8.3)
• GitHub Check: build-openlitespeed (8.2, lsphp82)
• GitHub Check: build-php (8.4)
• GitHub Check: build-openlitespeed (8.1, lsphp81)
• GitHub Check: build-openlitespeed (7.4, lsphp74)

🔇 Additional comments (3)

php/Dockerfile (3)

10-10: Consistent keyword casing for wpcli_builder.

Stage alias unchanged; COPY --from references remain valid.

---

22-22: Consistent keyword casing for builder stage.

No impact on downstream COPY --from=builder steps.

---

4-4: Resolved FromAsCasing — no functional change.
Verified: no lowercase "as" aliases remain in Dockerfiles (script output: OK: no lowercase 'as' aliases found).

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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