Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • TortoiseGit TortoiseGit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 381
    • Issues 381
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGitTortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #2562
Closed
Open
Issue created Aug 19, 2015 by Aurimas Vinckevicius@aurimasv

Automatically track remote when pushing untracked branch

It would be great to have an option to automatically check the "track" option when pushing an untracked branch to a remote repo.

I often create new topic branches locally, push them to GitHub, and create pull requests. Unfortunately, I usually forget to click the "track" option, so when the PR gets merged and I delete the remote branch, I have to manually go back and clean up my local branches.

I can see how tracking by default could be bad when pushing to remotes that are not entirely under your control. Someone else could delete a branch you are interested in and the deletion would propagate to your local repo during fetch. Maybe the pref could be repo-specific, though that creates another layer of complexity.

Edited Dec 26, 2021 by Sven Strickroth
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking