Subscription model with a possible Aha! listener

What is the challenge?

We have a scenario wherein Github is becoming Single Source of Truth for any changes. Our idea is that can Aha! have a listener. Listener will listen to any changes in Github. this will help changes in Aha! maintained. this can be through Publish-Subscribe model if needed so that transactions can be made asynchronously.

What is the impact?

Aha! and Github synchronization will be lost.

Describe your idea

We have a scenario wherein Github is becoming Single Source of Truth for any changes. Our idea is that can Aha! have a listener that will listen to any changes in Github by which changes can be updated in a custom table.