Fabric schedule as a separate item

I'm using pipelines with schedules. This works for me. 

But whenever I change a schedule, the pipeline appears as Uncommitted in the Fabric UI, and Source control tells me I've changed the pipeline.

That may be true, but the pipeline itself didn't change.

If I commit the change, it will go into the CI/CD process, and I risk promoting my schedule change from dev to production. And I'm very sure these two are different.

So, would it be possible to either ignore schedule changes for Git? Or move schedules out of the pipeline and host them at the workspace level. That way, I can reuse them if I want, but I can also control the deployment between environments by excluding them.