Skip to content

Commit

Permalink
README: update GPG keys
Browse files Browse the repository at this point in the history
  • Loading branch information
@jrfnl
jrfnl committed May 20, 2024
1 parent 124c9c4 commit 5c08b04
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ php phpcbf.phar -h
```

These Phars are signed with the official Release key for PHPCS with the
fingerprint `95DE 904A B800 754A 11D8 0B60 5E6D DE99 8AB7 3B8E`.
fingerprint `689D AD77 8FF0 8760 E046 228B A978 2203 05CD 5C32`.

### Composer
If you use Composer, you can install PHP_CodeSniffer system-wide with the following command:
Expand Down Expand Up @@ -76,8 +76,8 @@ You will then be able to run PHP_CodeSniffer from the vendor bin directory:
### Phive
If you use Phive, you can install PHP_CodeSniffer as a project tool using the following commands:
```bash
phive install --trust-gpg-keys 95DE904AB800754A11D80B605E6DDE998AB73B8E phpcs
phive install --trust-gpg-keys 95DE904AB800754A11D80B605E6DDE998AB73B8E phpcbf
phive install --trust-gpg-keys 689DAD778FF08760E046228BA978220305CD5C32 phpcs
phive install --trust-gpg-keys 689DAD778FF08760E046228BA978220305CD5C32 phpcbf
```
You will then be able to run PHP_CodeSniffer from the `tools` directory:
```bash
Expand Down

0 comments on commit 5c08b04

Please sign in to comment.