Can you explain what you mean when you say you are using 'CVS' from 'in Pega' ?
PRPC (to my knowledge - I could be wrong?) doesn't have any integration to CVS or any other source control system : PRPC does have it's own CHECK-IN/CHECK-OUT (and branching in later versions) mechanisms - but I wasn't aware of any CVS 'underneath' here ?
As per my understanding PRPC internally uses the CVS for CHECKIN/CHECKOUT. Instead of using the default mechanism of PRPC for checkin/checkout we want to check whether it can integrated with the GIT Source control. Please let me know if you have any insights on the same for using the GIT with PEGA.
This would allow somebody to build a GIT client that could interact with a GIT repository I'm sure - probably a fair amount of work - but possible I would say.
But I think you are asking "How could we manage our PRPC RULES in a GIT repository?": that is a different kettle of fish : PRPC rules are stored in the Database (not the filesystem): so if you wanted a system where PRPC would function as a GIT repository itself: that would require a significant re-implemenation of how we store and interact with rules/rulesets.....
That would make a great ENHANCEMENT ('feedback') request....but it would probably would be a non-trivial thing to deliver !