At its core, this tool has the bones to back-up / synchronize Jamf Pro critical files between any two REST APIs, right?
GitLab has it's own REST API.
It stands to reason that a variant of the methods used here could be forked to handle the specific URL / syntax differences, and version control of any Jamf Pro API accessible object should be possible if the GitLab project is formatted properly.
How hard could it be? 😅
(Miss you buddy)