Avoid running jobs if PR is documentation-related

[native-api]

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

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. 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

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 I know I can achieve this via shell scripts however would be nice if this was a first …