Change rector practice

Author: kenjis

README.md

@@ -143,8 +143,10 @@ predefined rulesets. Rector can be highly opinionated based on its configuration
 so be sure to read the documentation and figure out the best fit for you. This workflow performs
 a "dry run" to check for any changes that Rector would have made and fail if there are matches.
 
-> Note: Rector updates rules all the time so you may want to lock your repo to the latest known working version of Rector to prevent unexpected failures
-> E.g. in **Template/.github/workflows/rector.yml** supply the specific minor patch: `composer global require --dev rector/rector:0.12.16`
+> Note: Rector updates rules all the time, so you may want to lock your repo to
+> the latest known working version of Rector to prevent unexpected failures.
+> Using pinned version in `composer.json` and update it with dependabot is the
+> best practice.
 
 #### Unused
 

src/Template/.github/workflows/rector.yml

@@ -61,6 +61,4 @@ jobs:
           fi
 
       - name: Analyze for refactoring
-        run: |
-          composer global require --dev rector/rector:^0.15.1
-          rector process --dry-run --no-progress-bar
+        run: vendor/bin/rector process --dry-run --no-progress-bar