By default, a build email is sent to the committer and the author, but only if they have access to the repository the commit was pushed to. This prevents forks active on Travis CI from notifying the upstream repository’s owners when they’re pushing any upstream changes to their fork. It also prevents build notifications from going to folks not registered on Travis CI.

These reviewers are automatically added to pull requests that change files along those paths.

If you select
Required
next to a path entry, then the pull request cannot be completed until:

Select
Optional
if you want to add reviewers automatically, but not require their approval to complete the pull request.

When the required reviewers approve the code, you can complete the pull request.

In some cases, you need to bypass policy requirements so you can push changes to the branch directly. For these situations, grant the
Exempt from policy enforcement
permission to a user or group. You can scope this permission to an entire project, a repo, or a single branch. Manage this permission along the with other
Git permissions
.

Exempt from policy enforcement

Important

Users with
Exempt from policy enforcement permission
set to allow can complete pull requests even if the branch policy is not satisfied. Use caution when granting this permission, especially at the repo and team project level.

Q A

Can I push changes directly to a branch after a branch policy is configured?

I have the exempt from policy permission set, why am I still seeing policy failures in the pull request status?

Even for users that are exempt from policy enforcement, the configured policies are still evaluated when changes are added to a pull request. For exempt users, policy status is advisory only and will not block completion of the pull request.