The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to save the Pull request options and keep them saved for every pull?

Shatoria Poole
August 1, 2023

I'd like to know how or if there's a way to keep the settings I mark checked inside the Pull Options area whenever I initiate a new pull request instead of having to re-check the boxes every time I pull. Checking the boxes on every time gives room for human errors where a user may forget to check a box and breaking the application.

 

I'll attach a screenshot of the Pull request window and mark the settings in a red box that I'd like to keep checked at all times, even when a new pull request is initiated.

Pull request question.png

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Martin Runge
Community Champion
August 4, 2026

Hi @Shatoria Poole

As far as I know, Sourcetree does not remember the Pull Options checkboxes between pulls, because each one is a one-time flag passed to the underlying git command. The reliable way to make them "stick" is to set the matching git config values, which Sourcetree then respects automatically.

You can set these under Repository Settings or globally from a terminal:

  • Rebase instead of merge: git config pull.rebase true
  • Prune tracking branches: git config fetch.prune true
  • Always create a merge commit: git config merge.ff false

Add --global to any of these to apply them across every repository instead of just the current one.

Which of the options in your screenshot matter most to you, the rebase and prune ones, or the commit behaviour? That decides which config keys are worth setting.

Cheers, Martin

TAGS
AUG Leaders

Atlassian Community Events