Re-sync GitHub entities on a regular schedule | Voters

Re-sync GitHub entities on a regular schedule

Mark DeBeer

We have noticed that a number of changes in GitHub do not trigger a change in Port. For instance we archived a repo and that change was not reflected in Port. If we can't get updates for all these actions it would be nice to set a regular schedule to refresh the data and fill the gaps.

November 1, 2024

Simon Beaulieu

I remember reading somewhere in the documentations that the Github exporter worked on a schedule but also reacted to Push events. Unfortunately on our end we see that push events are sometimes missed and we lack visibility into why. Happy to know that I am not the only one experiencing these issues.

Matan Grady

Simon Beaulieu: Hi, you're definitely not the only one experiencing it. We understand the need and are working to improve both the docs and the integrations.
To clarify, indeed the Github action works on real-time events AND on-demand syncs (if you, from Port, click on "Resync" from the data sources tab).
Aside of repositories deletion (which I can also suggest a workaround for), all main events should be synced without a scheduled sync