OAuth PAT vs App Password in SourceTree: Which Supports Simple Credential Switching for Test Workflows?

When configuring SourceTree to test a Git integration without exposing production credentials, a user can create a limited‑scope personal access token (OAuth‑based PAT) or an Atlassian app password for a test repository. Both mechanisms are stored in the native OS credential store and are reused for subsequent operations on the same host.

The unresolved behavior is that SourceTree does not provide a built‑in way to force a re‑prompt or to select which stored credential to use for a particular remote after the initial authentication; switching between test and production credentials currently requires manual intervention in the OS store. This makes it difficult to verify that the test token is being actively used during verification steps.

Which of the two credential methods offers a more straightforward way to alternate between test and production credentials without editing the OS store? Does SourceTree expose any UI option to clear or override cached credentials for a specific host? Is there a configuration that causes SourceTree to request credentials on each fetch/pull for a given remote?