Restore c:c shortcut for cache:clean 2.4.8

[ajung2]

Summary

Dear Magento Development Team,

I would like to report an important developer experience issue with the Magento CLI that significantly impacts the daily development workflow.

Problem

In the current Magento CLI version 2.4.8, the shortcut php bin/magento c:c for the cache:clean command is no longer available. Instead, developers must now type out the full command php bin/magento cache:clean.

Impact on Developer Experience

This change results in:

• Reduced productivity: The cache clean command is used very frequently during development
• Unnecessary typing overhead: Developers now need to type 11 additional characters
• Workflow disruption: Established muscle memory no longer works

Technical Background

The issue appears to be caused by the new specific command cache:clean:payment_services_merchant_scopes that was added to the cache:clean namespace. This highly specific command will never be used by the vast majority of developers.

CLI output shows:

Available commands for the "cache:clean" namespace:
  cache:clean:payment_services_merchant_scopes  Clean Payment Services Merchant scopes cache

Examples

app@d254b067e603:~/html$ php bin/magento c:c        
Magento CLI 2.4.8

Usage:
  command [options] [arguments]

Options:
  -h, --help            Display help for the given command. When no command is given display help for the list command
  -q, --quiet           Do not output any message
  -V, --version         Display this application version
      --ansi|--no-ansi  Force (or disable --no-ansi) ANSI output
  -n, --no-interaction  Do not ask any interactive question
  -v|vv|vvv, --verbose  Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug

Available commands for the "cache:clean" namespace:
  cache:clean:payment_services_merchant_scopes  Clean Payment Services Merchant scopes cache

Proposed solution

I kindly request that you restore the c:c shortcut for cache:clean. Possible approaches:

1. Namespace reorganization: Move the Payment Services command to its own namespace
2. Alias restoration: Define explicit aliases for frequently used commands
3. Priority-based shortcuts: Give precedence to commonly used commands for shortcuts

Justification

• The cache:clean command is one of the most frequently used CLI commands in Magento development
• Developer experience should not be impacted by very specific, rarely used commands
• Backward compatibility for established workflows is important for the developer community

I hope for your understanding of this issue and a timely solution in an upcoming update.

Release note

Additional Information:

• Magento CLI Version: 2.4.8
• Operating System: Ubuntu 24.04.2 LTS
• PHP Version: 8.3

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @ajung2. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @ajung2 ,

Thank you for your report and collaboration.

We have verified the issue using the latest 2.4-develop branch and found that the issue is not reproducible in this version. However, the issue is reproducible in version 2.4.8, as Verify the attached screenshot for more reference.

Tested Versions:

✅ 2.4-develop – Issue not observed

❌ 2.4.8 – Issue confirmed

Steps to Reproduce:

• Open the CLI.
• Run the following command:
  php bin/magento c:c

Additional Information
Following these steps, we were able to reproduce the issue in version 2.4.8.

Hence, we are marking this as: "Issue: Confirmed"

Thank you once again for your support!