Forum Discussion
Git Branching with active Schedules
Hi Anonymous,
Haha, yes it does feel like someone has gone git happy 😄 I wish they'd focus on Lakehouse git version integration instead.
Yes, we've gone for a similar solution. In the develop branch, which is the branch we all pull from, we have the committed versions of the schedules turned off, but then turn them back on in the workspace. So unfortuantly we have to live with the uncommited icon noficiations in the workspace, which is annoying, but we can live with.
Only our Dev workspace is backed by git, the develop branch. The code is pushed into other workspaces by our DevOps deployment pipelines. Or you can use the Fabric deployment pipelines too. So turning on/off schedules in Dev workspace does not affect the test and production workspaces.
Hi caseybks,
This is a valid problem, and I don't think there is an immediate solution other than to adjust your process.
I do question why you have things schedueld in DEV however. In my enviornment, we don't schedule anything in DEV as it's used purely for development. Once we are ready to start testing it with data on a scheduled basis and not ad-hoc, we promote it to TST which is where things are scheduled. This prevents the issue you are encountering, but is a pretty big process shift from what you're currently doing it seems.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.