---
title: Pull request workflow hooks
description: "Workzone pull request workflow hooks control how teams interact with pull request changesets: ![](https://izymes.com/wp-content/uploads/2022/07/Workzone-Settings-e1730855078830.png) 1. Allow or block push operations to a branch once a pull request has been created. 2. Unapprove Pull Requests on any Source branch commit 3.…"
url: "https://izymes.com/docs/properties/"
updated: "2026-04-07"
category: Feature Guide Workzone
---

# Pull request workflow hooks

Workzone pull request workflow hooks control how teams interact with pull request changesets:

![](https://izymes.com/wp-content/uploads/2022/07/Workzone-Settings-e1730855078830.png)

1. Allow or block push operations to a branch once a pull request has been created.
2. Unapprove Pull Requests on any Source branch commit
3. Unapprove Pull Requests on Source branch code change
4. Unapprove Pull Requests on Target change
5. Enforce merge condition

#### Push after pull request

- **Enable**: Users can push to the source branch that has an active outgoing pull request. The pull request is updated.
- **Disable**: Users are not allowed to push to a branch the has an active outgoing pull request. Git push will be rejected.

#### Unapprove Pull Requests on any Source branch commit

This setting can only be activated if ‘Push after pull request’ is allowed. Activating this setting will deactivate "Unapprove Pull Requests on Source branch code change"

- **Enable:**Revoke pull request approvals on _any_ source branch commit, even if it was a rebase without code changes
- **Disable: **Do not revoke pull request approvals on _any_ source branch commit, even if it was a rebase without code changes

#### Unapprove Pull Requests on *Source* branch code change

This setting can only be activated if ‘Push after pull request’ is allowed.

- **Enable**: After pushing changes to a source branch with an outgoing pull request, given approvals matching [reviewer files/paths](https://izymes.com/docs/workzone-add-file-and-group-reviewers-to-your-pull-requests/) of the update's change-set will be withdrawn. All matched reviewers need to re-approve the pull request. Non-matching approvals are not affected.
- **Disable**: After the source branch of an active pull request has been updated, given approvals are not reset.

#### Unapprove Pull Requests on Target change

When an active pull request's *destination* branch commit status changes through a merge or otherwise, the pull request is re-scoped. This is as important as resetting approvals on source branch changes as the effective diff for the pull request changes, which makes another review desirable.

- **Enable**: After pull request rescope, all given approvals (if any) will be withdrawn. All reviewers need to re-approve the pull request.
- **Disable**: After pull request rescope, given approvals are not reset.

#### Enforce merge conditions

Enables a repository wide merge check hook that enforces Workzone merge conditions before a pull request can be merged.

#### Workflow details

This section will outline the Workzone rules in an easy-to-read format and the workflow taking place after a pull request has been created. 

These rules are updated in real-time and can be used as a reference guide when configuring the above Workflow Properties. 

![](https://izymes.com/wp-content/uploads/2022/07/Workflow-Details.png)

   [Try Workzone!](https://marketplace.atlassian.com/apps/1211303/workzone-pullrequest-workflow?hosting=datacenter&tab=overview)