Jonas DOREL
fd29bfc7c5
Without `--ignore-unknown`, files without an extension or with an unknown extension would trigger the following error : ``` .gitignore[error] No parser could be inferred for file: ansible.cfg ```
142 lines
4.7 KiB
Markdown
142 lines
4.7 KiB
Markdown
---
|
||
id: precommit
|
||
title: Pre-commit Hook
|
||
---
|
||
|
||
You can use Prettier with a pre-commit tool. This can re-format your files that are marked as “staged” via `git add` before you commit.
|
||
|
||
## Option 1. [lint-staged](https://github.com/okonet/lint-staged)
|
||
|
||
**Use Case:** Useful for when you want to use other code quality tools along with Prettier (e.g. ESLint, Stylelint, etc.) or if you need support for partially staged files (`git add --patch`).
|
||
|
||
_Make sure Prettier is installed and is in your [`devDependencies`](https://docs.npmjs.com/specifying-dependencies-and-devdependencies-in-a-package-json-file) before you proceed._
|
||
|
||
```bash
|
||
npx mrm lint-staged
|
||
```
|
||
|
||
This will install [simple-git-hooks](https://github.com/toplenboren/simple-git-hooks) and [lint-staged](https://github.com/okonet/lint-staged), then add a configuration to the project’s `package.json` that will automatically format supported files in a pre-commit hook.
|
||
|
||
Read more at the [lint-staged](https://github.com/okonet/lint-staged#configuration) repo.
|
||
|
||
## Option 2. [pretty-quick](https://github.com/azz/pretty-quick)
|
||
|
||
**Use Case:** Great for when you want an entire file formatting on your changed/staged files.
|
||
|
||
Install it along with [husky](https://github.com/typicode/husky):
|
||
|
||
<!--DOCUSAURUS_CODE_TABS-->
|
||
<!--npm-->
|
||
|
||
```bash
|
||
npm install --save-dev pretty-quick husky
|
||
```
|
||
|
||
<!--yarn-->
|
||
|
||
```bash
|
||
yarn add --dev pretty-quick husky
|
||
```
|
||
|
||
<!--END_DOCUSAURUS_CODE_TABS-->
|
||
|
||
Add this to your `package.json`:
|
||
|
||
```json
|
||
{
|
||
"husky": {
|
||
"hooks": {
|
||
"pre-commit": "pretty-quick --staged"
|
||
}
|
||
}
|
||
}
|
||
```
|
||
|
||
Read more at the [pretty-quick](https://github.com/azz/pretty-quick) repo.
|
||
|
||
## Option 3. [pre-commit](https://github.com/pre-commit/pre-commit)
|
||
|
||
**Use Case:** Great when working with multi-language projects.
|
||
|
||
Copy the following config into your `.pre-commit-config.yaml` file:
|
||
|
||
```yaml
|
||
- repo: https://github.com/pre-commit/mirrors-prettier
|
||
rev: "" # Use the sha or tag you want to point at
|
||
hooks:
|
||
- id: prettier
|
||
```
|
||
|
||
Read more at [mirror of prettier package for pre-commit](https://github.com/pre-commit/mirrors-prettier) and the [pre-commit](https://pre-commit.com) website.
|
||
|
||
## Option 4. [git-format-staged](https://github.com/hallettj/git-format-staged)
|
||
|
||
**Use Case:** Great for when you want to format partially-staged files, and other options do not provide a good fit for your project.
|
||
|
||
Git-format-staged is used to run any formatter that can accept file content via stdin. It operates differently than other tools that format partially-staged files: it applies the formatter directly to objects in the git object database, and merges changes back to the working tree. This procedure provides several guarantees:
|
||
|
||
1. Changes in commits are always formatted.
|
||
2. Unstaged changes are never, under any circumstances staged during the formatting process.
|
||
3. If there are conflicts between formatted, staged changes and unstaged changes then your working tree files are left untouched - your work won’t be overwritten, and there are no stashes to clean up.
|
||
4. Unstaged changes are not formatted.
|
||
|
||
Git-format-staged requires Python v3 or v2.7. Python is usually pre-installed on Linux and macOS, but not on Windows. Use git-format-staged with [husky](https://github.com/typicode/husky):
|
||
|
||
<!--DOCUSAURUS_CODE_TABS-->
|
||
<!--npm-->
|
||
|
||
```bash
|
||
npm install --save-dev git-format-staged husky
|
||
```
|
||
|
||
<!--yarn-->
|
||
|
||
```bash
|
||
yarn add --dev git-format-staged husky
|
||
```
|
||
|
||
<!--END_DOCUSAURUS_CODE_TABS-->
|
||
|
||
and add this config to your `package.json`:
|
||
|
||
```json
|
||
{
|
||
"husky": {
|
||
"hooks": {
|
||
"pre-commit": "git-format-staged -f 'prettier --ignore-unknown --stdin --stdin-filepath \"{}\"' ."
|
||
}
|
||
}
|
||
}
|
||
```
|
||
|
||
Add or remove file extensions to suit your project. Note that regardless of which extensions you list formatting will respect any `.prettierignore` files in your project.
|
||
|
||
To read about how git-format-staged works see [Automatic Code Formatting for Partially-Staged Files](https://www.olioapps.com/blog/automatic-code-formatting/).
|
||
|
||
## Option 5. Shell script
|
||
|
||
Alternately you can save this script as `.git/hooks/pre-commit` and give it execute permission:
|
||
|
||
```sh
|
||
#!/bin/sh
|
||
FILES=$(git diff --cached --name-only --diff-filter=ACMR | sed 's| |\\ |g')
|
||
[ -z "$FILES" ] && exit 0
|
||
|
||
# Prettify all selected files
|
||
echo "$FILES" | xargs ./node_modules/.bin/prettier --ignore-unknown --write
|
||
|
||
# Add back the modified/prettified files to staging
|
||
echo "$FILES" | xargs git add
|
||
|
||
exit 0
|
||
```
|
||
|
||
If git is reporting that your prettified files are still modified after committing, you may need to add a [post-commit script to update git’s index](https://github.com/prettier/prettier/issues/2978#issuecomment-334408427).
|
||
|
||
Add something like the following to `.git/hooks/post-commit`:
|
||
|
||
```sh
|
||
#!/bin/sh
|
||
git update-index -g
|
||
```
|