# Deploy to GitHub multiple files from multiple Travis jobs on different conditions

**URL:** <https://travis-ci.community/t/deploy-to-github-multiple-files-from-multiple-travis-jobs-on-different-conditions/5091>\
**Category:** Deployment\
**Created:** [September 13, 2019, 1:07pm UTC](https://travis-ci.community/t/deploy-to-github-multiple-files-from-multiple-travis-jobs-on-different-conditions/5091 "2019-09-13T13:07:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [September 13, 2019, 4:03pm UTC](https://travis-ci.community/t/deploy-to-github-multiple-files-from-multiple-travis-jobs-on-different-conditions/5091/2 "2019-09-13T16:03:54Z")

</div>

A `deploy:` clause is a part of a job description.

So if you need to deploy at multiple moments, you’ll need to make sure that all relevant jobs have a `deploy:` clause with an appropriate content, this way or another.

The ways are:

- A `deploy:` at global level will be inherited by all jobs.
- A `deploy:` at `matrix: include:` level will be private for the job

The clause cannot be inherited in parts – a job-level clause fully overrides a global one. So you either

- make a global `deploy:` clause with a structure general enough to fit all jobs
  - E.g. `condition:` can have logical ORs; or

- specify `deploy:` manually in each affected job which would probably lead to some duplication.

---

_[View the full topic](https://travis-ci.community/t/deploy-to-github-multiple-files-from-multiple-travis-jobs-on-different-conditions/5091)._