Skip to content

Settings and activity

2 results found

  1. 207 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Avinash Bookwala commented  · 

    As a workaround, we use a combination of SQL Source Control and SourceTree. SQL Source control to push changes to the (in your case) origin/test branch, and SourceTree to pull changes from the origin/master branch to the local test branch.

    An error occurred while saving the comment
    Avinash Bookwala commented  · 

    With the recent addition of the ability to pull and push changes to/from a remote repository in Git, it would also be very useful to configure the branch to pull and push changes from or to rather than use the same branch for both purposes.

    For example I may want to always pull changes from the trunk or master branch, but may want to push changes to another branch which after review may get merged manually into the trunk or master branch.

    Avinash Bookwala supported this idea  · 
  2. 92 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Avinash Bookwala supported this idea  ·