Skip to content

Update stop on failure README section #116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BrainMaestro merged 1 commit into from
Feb 15, 2021
Merged

Update stop on failure README section #116

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,8 +54,7 @@ All commands have global support (besides testing the hooks. Still requires bein

#### Stop on failure

When a hook is a sequence of commands, it can be useful to stop the execution when
a command fails.
When a hook is a sequence of commands, it can be useful to stop the execution when a command fails.

Specify the impacted hooks in the `stop-on-failure` config section.

Expand All @@ -75,6 +74,8 @@ Specify the impacted hooks in the `stop-on-failure` config section.
}
```

Always be sure to run the [update command](#updating-hooks) after changing the `stop-on-failure` config section.

#### Shortcut

Add a `cghooks` script to the `scripts` section of your `composer.json` file. That way, commands can be run with `composer cghooks ${command}`. This is ideal if you would rather not edit your system path.
Expand Down