Hello Siddharth Joshi,
Currently, Purview doesn't support connecting to a DevOps Repo to promote code changes from one environment to another.
However, here is a document that identifies common tasks that can help deploy Azure Purview into higher environments: Azure Purview deployment best practices and deployment models
You can follow this document to deploy artifacts from one environment to another. This involves exporting the Purview artifacts from the source environment, storing them in a version control system, and then deploying them to the target environment using the Purview REST API.
I see below similar items in the purview feedback channel for this feature request.
All the feedback shared in this forum is actively monitored and reviewed by respective product owners, which would be open for the user community to upvote & comment on. This allows product teams to prioritize your idea against our existing feature backlog effectively and gives insight into the potential impact of implementing the suggested feature.
I suggest up-voting and commenting on this feedback item for more visibility.
I hope this info helps.
A similar thread has been discussed here
Please let me know if you have any further questions.
If this answers your question, please consider accepting the answer by hitting the Accept answer and up-vote as it helps the community look for answers to similar questions.