# GitHub pages deployment fails with "missing github\_token"

**URL:** https://travis-ci.community/t/github-pages-deployment-fails-with-missing-github-token/5955
**Category:** Deployment
**Created:** [November 15, 2019, 5:18am UTC](https://travis-ci.community/t/github-pages-deployment-fails-with-missing-github-token/5955 "2019-11-15T05:18:25Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)
#### Post date: [November 15, 2019, 7:46pm UTC](https://travis-ci.community/t/github-pages-deployment-fails-with-missing-github-token/5955/3 "2019-11-15T19:46:49Z")

</div>

This is a bug in build config validation – it breaks configs for some v1 deployers.

Disable build config validation or [opt in for dpl v2](https://docs.travis-ci.com/user/deployment-v2) which does work with the “fixed” config.

> [@"missing api\_key" when deploying to GitHub releases](https://travis-ci.community/t/missing-api-key-when-deploying-to-github-releases/5761/7):
>
> Yes, I’m completely sure this the configuration for this build. This is what I see in “view config” tab. But I just noticed there’s also this suspicious message under “build config validation”: jobs.include.deploy: key api\_key is an alias for token, using token

---

_[View the full topic](https://travis-ci.community/t/github-pages-deployment-fails-with-missing-github-token/5955)._