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 382
    • Issues 382
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • 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
  • #746
Closed
Open
Issue created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

Make tortoisegit more gerrit friendly

By imsan... on March 14, 2011 10:11 (imported from Google Code)


We use tortoisegit with gerrit (http://code.google.com/p/gerrit/) code review.

Some small changes would help to improve our workflow.

To create a review in Gerrit you have to push to refs/for/branchname/optional-topic (See http://gerrit.googlecode.com/svn/documentation/2.1.6/user-upload.html)

The Remote combobox in the push dialog is too small to show this long string and it's hard to choose the right one, on reselect.

Maybe it would be also a good idea to mark a remote as gerrit server and only allow to push to refs/for/*

Gerrit use a Change-id (http://gerrit.googlecode.com/svn/documentation/2.1.6/user-changeid.html) to identify the commits for the same review.

On cherry-picking to backport a change to an older version we have to manually delete these change-id (with rebase). It would be nice, if the cherry-pick dialog would ask to remove it (if a change-id exists)

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