We have a mono-repo, every project has a different dev branch but a common prod branch(main). New features get added to dev branches, once ready will merge to main for prod deployment.
If a common static config file is used, the main branch will keep on changing as independent projects change the main branch frequently, and merge conflicts on the config.yml file will become a pain.
Heard about dynamic config generation using the setup workflows, we can have different config file per branch that removes the merge conflict as well as provides an abstraction to other projects <>.yml since each project has its own config file.
But Inside a project, we need to trigger workflows based on files for folder changes. Any idea on how to do this from generated config ?
I tried using swissknife/trigger-workflows-for-all-modified in the generated config , but I believe internally it’s using APIs to trigger workflows. I believe the orb always invokes workflows in config.yml at the root. So it tries to invoke workflows from generated config and checks in config.yml at the root which results in an error.
Can anyone please provide me any idea or suggestions on how to handle this scenario?