Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
TortoiseGit
TortoiseGit
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 301
    • Issues 301
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 8
    • Merge requests 8
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #150

Closed
Open
Created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

When pushing, 'remote' should default to the tracked branch, or empty

By jaffathec... on August 24, 2009 16:45 (imported from Google Code)


(1.9.1)

When I select 'push' while on my local master branch, the default in "remote"
is "RB_1.6". This has led to me accidentally pushing to the wrong remote
branch.

The "remote" option should be empty by default in my opinion. This means it
pushes to whatever remote branch the local branch is tracking. This is the
usual case.

The less-usual case is pushing to a branch you're not tracking, at this point
the user should have to select a remote branch to push to, the GUI should not
assume a particular branch.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None