# Avoid running jobs if PR is documentation-related **URL:** \ **Category:** Travis CI Discussions & Feedback\ **Tags:** travis-build\ **Created:** [July 15, 2020, 4:35pm UTC](https://travis-ci.community/t/avoid-running-jobs-if-pr-is-documentation-related/9350 "2020-07-15T16:35:37Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [July 15, 2020, 5:02pm UTC](https://travis-ci.community/t/avoid-running-jobs-if-pr-is-documentation-related/9350/2 "2020-07-15T17:02:54Z")
Consider upvoting the below FR – it would allow you to quit the job before the installation logic fires. > [@Run a chunk of user code before the stock installation logic](https://travis-ci.community/t/run-a-chunk-of-user-code-before-the-stock-installation-logic/4141): > > As it is now, stock installation logic (platform install, build addons) run before any user-supplied code gets control. As a consequence, if that logic doesn’t quite fit the needs or something goes wrong with it, all a user can do is ditch it altogether – they can’t do anything about the problem. I’m suggesting to run some user-supplied code before any stock logic fires, [except perhaps cache restoration.](https://travis-ci.community/t/allow-jdk-install-jdk-sh-to-use-the-build-cache/3145) before\_install looks like the perfect candidate: before\_install: – stock logic – install: w… Possible duplicate of > [@Ability to run jobs depending on what files are changed](https://travis-ci.community/t/ability-to-run-jobs-depending-on-what-files-are-changed/3572): > > Hello, I would like to request a feature which would allow us to run certain jobs based on what files have been changed. This would allow people to use a monorepo approach to version control for related applications and not waste CI resources testing every application if only a single application is changed. Example config which would be ideal: [https://gist.github.com/klj613/f4f8a2e72b59af504939f17fbaf5b441](https://gist.github.com/klj613/f4f8a2e72b59af504939f17fbaf5b441) I know I can achieve this via shell scripts however would be nice if this was a first … --- _[View the full topic](https://travis-ci.community/t/avoid-running-jobs-if-pr-is-documentation-related/9350)._