Ability to use dynamic config.yml based on conditions

So currently we have only one GitHub branch (master) and one circle ci config.yml. We have a scheduled trigger to run the pipeline daily. Now we are trying to have multiple branches for multiple environments, which will use different circle-ci config.yml. (Having a develop branch(staging env) and master branch (prod env)). So whenever a PR gets created to merge feature branch into develop branch it should use config1 and when creating a PR for merging develop branch into master, it should use config2 and the daily running trigger should continue to use default config.yml. Did anyone came across such scenario earlier. Thanks for your help in advance!

1 Like

Circleci has a solution that it calls Dynamic Configuration, I’ve not used it so can not comment on the detail, but the starting point is

which then leads on to

1 Like