Skipping a deployment with the pages provider because the current build is a pull request

I want to deploy in any branch but it failure every time and a receive this message:

Skipping a deployment with the pages provider because the current build is a pull request.

this is the url :
https://travis-ci.org/batouche-dev/dashboard/builds/643532053?utm_source=github_status&utm_medium=notification

and travis config:

dist: trusty
sudo: false

language: node_js
node_js:
  - "13.6.0"

addons:
    chrome: stable

cache:
  directories:
     - ./node_modules

install:
  - npm install

script:
  - npm run test:cover -- --watch=false --progress=false --browsers=ChromeHeadlessCI
  - npm run test -- --watch=false --progress=false --browsers=ChromeHeadlessCI
  - npm run e2e -- --protractor-config=./e2e/protractor-ci.conf.js

after_success:
   - npm run coveralls
    - npm run build:gh-pages:test1


deploy:
  provider: pages
  skip_cleanup: true
  github_token: $GITHUB_TOKEN  # Set in the settings page of your repository, as a secure variable
  local_dir: gh-pages
  on:
    branch: feat/gh-pages-with-travis

What are you asking? As the message plainly says, and as documented in


PR builds such as this will not trigger deployments. Someone (including you!) would have to run a push build.

it not clear, i mean who can modify the configuration to get an automatic deploy?

If you run a push build, it would run deployment. https://travis-ci.org/batouche-dev/dashboard/requests?utm_medium=notification&utm_source=github_status shows that this feature branch’s push build requests are rejected because the branch name contains gh-pages.

Imprint