Rule based PR preview env deployment

Issues information

  • OS:
  • databases:
  • Programming language and version:
  • Link to your project on Github/Gitlab:
  • Link to your application - starting with

Your issue

How can I set rules on PR deployments?


“Do not deploy drafts”

Dockerfile content (if any)

specify here your dockerfile content

You’d just put drafts in a separate branch. Right?

Hi @Andreas_Asprou, did you check this documentation > Deployment Rule | Docs | Qovery ?

I’m not sure what you mean.

To be clearer, I don’t want to deploy PRs that are in Github’s draft state. But when they move into “ready for review”, I’d like to deploy it

This would work for PR names, I guess we can have a naming convention for deploying PRs.

If I change the name of a pr, does Qovery trigger?


“Only deploy PRs that contain [PREV]”

  1. Open PR named “Test”
  2. Qovery doesn’t deploy
  3. Rename PR to “Test [PREV]”
  4. Qovery deploys?

I’ve created my own flow for this with the Qovery & Git APIs, so this can be closed for my use case

1 Like