Skip to content
GitTree
العربية
Preferences

Configure integration refresh

Preferences › Integrations controls how GitTree reads your hosting accounts: how old the lists may get before Refresh pull requests, issues and checks, whether to Refresh when I come back, CI/CD log defaults, and where author pictures come from. Reading happens only while GitTree’s window is in front.

ProUpdated

Needs GitTree Pro or a running trial; Free keeps every local Git feature. Compare the plans.

On this page
  1. Before you start
  2. Where to find it
  3. Steps
  4. Expected result
  5. If something goes wrong
  6. Questions
  7. Related

Before you start

  • GitTree Pro or a running trial for hosting integrations.

Where to find it

  • Preferences › Integrations.
ActionmacOSWindows and Linux
Preferences⌘,Ctrl+,

Steps

  1. Set the refresh interval

    Choose how old lists may get under Refresh pull requests, issues and checks. A longer interval sends fewer requests to the provider.

  2. Refresh on return

    Keep Refresh when I come back on to re-read what is at least 15 seconds old when GitTree comes to the front or you switch repository tabs.

  3. Choose the CI/CD defaults

    Set Show log timestamps, Wrap long log lines and Watch runs I start or re-run.

  4. Choose avatars

    Avatars from connected accounts shows pictures from GitHub or Bitbucket; Avatars from Gravatar sends a hash of each author’s email to Gravatar and is off by default.

Expected result

Lists stay as fresh as you need without using up the provider’s request limits.

If something goes wrong

“The provider limits requests until …”

GitTree pauses and asks again after that time. A longer refresh interval avoids it.

Questions

Can GitTree show public GitHub pull requests without an account?

Yes, with Read public GitHub repositories without an account: off by default, and its requests carry no credentials.

Related