Currently, the X2A-publish is responsible for it's own git client. Following the ADR on the x2a backend soloution, all git actions will be taken via the k8s job that is created by the backend. thus, the publish would need to (1) decouple AAP integration from Git actions (2) remove git actions (3) handle the aap logic after the github was updated (2 tier command?)