fix(docs): Update Rector command in composer.json to remove unnecessary 'src' argument.

[terabytesoftw]

Pull Request

Q	A
Is bugfix?	✔️
New feature?	❌
Breaks BC?	❌

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Bug Fixes

  • Resolved an issue in the code processing tool configuration.

• Documentation

  • Updated changelog documenting recent bug fixes.

• Chores

  • Simplified development tooling scripts for improved maintainability.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Walkthrough

The Rector command in composer.json is updated to remove the 'src' argument from the process command. This change is documented in the CHANGELOG under a new Bug #122 entry.

Changes

Cohort / File(s)	Summary
Documentation CHANGELOG.md	Added changelog entry for Bug #122 documenting the removal of 'src' argument from the Rector command
Configuration composer.json	Updated rector script command from ./vendor/bin/rector process src to ./vendor/bin/rector process, removing unnecessary 'src' argument

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A Rector command, once wrapped tight,
Now hops freely, leaner and light,
The 'src' argument bid adieu,
CHANGELOG sings the tale so true! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating the Rector command in composer.json to remove an unnecessary 'src' argument, which aligns perfectly with the changeset.
Description check	✅ Passed	The description confirms the bugfix nature of the change and is directly related to the changeset modifications in composer.json and CHANGELOG.md.
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.}

---

📜 Recent review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 60bfe3a and b8f39ad.

📒 Files selected for processing (2)

• CHANGELOG.md
• composer.json

🧰 Additional context used

🧠 Learnings (3)

📓 Common learnings

Learnt from: terabytesoftw
Repo: php-forge/actions PR: 67
File: .github/workflows/phpstan.yml:13-16
Timestamp: 2025-09-29T14:58:04.095Z
Learning: In the php-forge/actions repository, the maintainer prefers using "composer update" as the default command in CI workflows to ensure the latest dependencies are always installed, rather than using "composer install" for reproducibility.

Learnt from: terabytesoftw
Repo: php-forge/foxy PR: 115
File: tests/Fallback/AssetFallbackTest.php:158-189
Timestamp: 2026-01-23T11:22:07.261Z
Learning: User terabytesoftw prefers not to use aliases when importing classes in PHP. They are comfortable with either fully-qualified class names or direct imports without aliases.

Learnt from: terabytesoftw
Repo: php-forge/support PR: 12
File: src/TestSupport.php:0-0
Timestamp: 2025-08-18T20:13:33.518Z
Learning: User terabytesoftw prefers clean trait-based designs over maintaining backward compatibility wrappers when refactoring utility classes in the php-forge/support project.

Learnt from: terabytesoftw
Repo: php-forge/actions PR: 65
File: .github/workflows/composer-require-checker.yml:80-83
Timestamp: 2025-09-28T15:12:48.345Z
Learning: The user terabytesoftw prefers using floating tags like v1 for third-party actions in GitHub workflows instead of pinning to specific commit SHAs, even when it's a security best practice to pin to immutable commits.

📚 Learning: 2025-09-29T14:58:04.095Z

Learnt from: terabytesoftw
Repo: php-forge/actions PR: 67
File: .github/workflows/phpstan.yml:13-16
Timestamp: 2025-09-29T14:58:04.095Z
Learning: In the php-forge/actions repository, the maintainer prefers using "composer update" as the default command in CI workflows to ensure the latest dependencies are always installed, rather than using "composer install" for reproducibility.

Applied to files:

• composer.json

📚 Learning: 2026-01-23T11:09:08.789Z

Learnt from: terabytesoftw
Repo: php-forge/foxy PR: 115
File: composer.json:68-77
Timestamp: 2026-01-23T11:09:08.789Z
Learning: When a composer.json in php-forge repositories references external template repos in sync-metadata scripts, prefer using the main branch reference rather than pinning to specific commit SHAs or tags. This reduces maintenance when upstream templates change, but be aware of potential drift; document rationale and review changes periodically.

Applied to files:

• composer.json

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

• GitHub Check: mutation / PHP 8.5-ubuntu-latest
• GitHub Check: phpunit / PHP 8.5-windows-2022
• GitHub Check: phpunit / PHP 8.5-ubuntu-latest
• GitHub Check: phpunit / PHP 8.4-ubuntu-latest
• GitHub Check: phpunit / PHP 8.3-ubuntu-latest
• GitHub Check: phpunit / PHP 8.1-windows-2022
• GitHub Check: linter / Super Linter
• GitHub Check: phpunit / PHP 8.1-ubuntu-latest
• GitHub Check: linter / Super Linter
• GitHub Check: mutation / PHP 8.5-ubuntu-latest

🔇 Additional comments (2)

CHANGELOG.md (1)

6-6: LGTM!

The changelog entry follows the established format and accurately documents the removal of the unnecessary 'src' argument from the Rector command.

composer.json (1)

77-77: LGTM!

Removing the 'src' argument is correct. Rector will use the paths defined in rector.php configuration (src and tests directories), which is the recommended approach for centralizing path configuration.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (60bfe3a) to head (b8f39ad).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@             Coverage Diff             @@
##                main      #122   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity       359       359           
===========================================
  Files             26        26           
  Lines            823       823           
===========================================
  Hits             823       823           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.