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 380
    • Issues 380
    • 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
  • #2049
Closed
Open
Issue created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

Add pull to after commit actions

By dmpra... on December 26, 2013 16:59 (imported from Google Code)


After using TortoiseGit for several months, I have the following requests for workflow improvements:

  1. The "Browse References" dialog is very useful. It would be nice if there were a menu option to take me directly there instead of having to go to a screen that I don't want (like Switch/Checkout) as a via-point.

  2. The workflow around Commit-Pull/Push has issues. In an ideal world, the workflow would be the following:

Commit
Pull (Merge)
Push

It seems that using the shortcuts, you can only do the following win TortoiseGit:

Commit
Push
If the Push Failed, Pull
Manually perform a push again.

Ideally, the entire process of getting changes from your WC to a single remote should be possible by being prompted and given shortcuts. Why can't we pull directly from the commit finished window? This is probably most important since 9 times out of 10, I'll need to pull before I can push. If a push fails and I am given the option to pull, I should be able to push again without going through the menuing system. Maybe if the merge fails or no-commit was selected, then don't, but in general either the above or the following should be possible without having to through the Explorer Menus more than once:

Commit
Push (Fails)
Pull (Merge succeeds)
Push (Succeeds)

  1. The way that I work, I often have lots of un-committed changes, and when I go to commit them, I do it piece-meal so that there is a changeset and comment for each part. I know this isn't ideal, but it's the way that I work some times. When committing, it would be nice if there were an option on the commit dialog to leave the dialog open after the commit. That way, I can select commit, have six files show up, select three, commit, then sollect the other three and commit again, without having to manually bring the window back up and wait for it to refresh.

  2. How can I set the default remote for pull operations? In some places I can set the default remote for a repo or branch, but I cannot seem to do that in the Pull dialog, and always have to change it (I have a new main bare repo, but leave the old one there for consistancy).

Thank you, and please accept this as a list of feature requests to improve a useful product, not complaints.

dmp

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