Atom GitHub Package: Local Git State vs Remote API Sync Timing

Determine the exact moment when a commit made through Atom’s built‑in Git interface is reflected in the remote repository state exposed by the GitHub API.

The GitHub package relies on the locally installed Git binary for version‑control operations and stores OAuth credentials in the OS keychain. Because Atom is no longer receiving official updates, the synchronization logic may depend on implicit triggers such as file‑save events, explicit 'Sync' commands, or the underlying Git push/fetch behavior, which can vary with network availability and keychain state.

Does the package automatically push commits to the remote after each local commit? Does it fetch remote references periodically to keep issue and pull‑request views up to date? What conditions cause a delay or discrepancy between the local Git state and the GitHub API representation?