7 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

You'll receive a confirmation email with a link to create a password (optional).

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Aran Deltac commented  ·  Jul 18, 2011 7:42 am  ·  Flag as inappropriate  ·  Delete

  Hmm, this is marked as completed, yet as far as I can tell addchangelist does not support git. Am I missing something?

• chris.nelson commented  ·  Feb 24, 2010 1:01 pm  ·  Flag as inappropriate  ·  Delete

  I'm just investigating CodeCollaborator so I can't speak intelligently about how it works but I can tell you how we've been using Gerrit (an open-source review tool).

  When a developer is ready for a review, they push to a special repository. Gerrit sees the push and creates a review. Gerrit allows you to configure default reviewers for certain modules or the submitter can request/assign a reviewer. The review process seems a lot like CC. When the change is approved (perhaps after revision), Gerrit pushes it to the main repo on behalf of the submitter.

  We're not entirely happy with this work flow. It's too detached from our Trac-based ticket system and it only really works for pre-commit reviews. We want something that integrates better (it seems like CC triggers can do that) and something that supports post-commit reviews. For example, when fast tracking a change for a tester or customer to try out, we'd like to be able to commit and build but track that the change was unreviewed and come back later to review and possibly revise it.

• Admingsporar (Admin, Code Collaborator) commented  ·  Apr 09, 2009 9:07 am  ·  Flag as inappropriate  ·  Delete

  As pjz noted, version 5.0 has support for addgitdiffs, so this is partially complete.

• Adminpjz (Admin, Code Collaborator) commented  ·  Dec 04, 2008 1:37 pm  ·  Flag as inappropriate  ·  Delete

  5.0 will have an addgitdiffs command, analogous to the addsvndiffs command.

• jasedit commented  ·  Nov 04, 2008 11:20 am  ·  Flag as inappropriate  ·  Delete

  I currently use the addchanges command almost exclusively, so that would be my highest rated command personally.

• jasedit commented  ·  Nov 04, 2008 11:00 am  ·  Flag as inappropriate  ·  Delete

  For me at least, I'd like to see it treated just like svn. Granted, I only use git as a front-end to a svn server, so there may be more complicated uses of git that don't fit this workflow. But that's the big thing for me - being able to point at a git repository and use it with the gui and such.

• Adminjasoncohen (Admin, Code Collaborator) commented  ·  Nov 03, 2008 12:25 pm  ·  Flag as inappropriate  ·  Delete

  It's funny that there are so many votes and no comments.

  Would anyone like to share exactly how they'd like to see the implementation work? How would it fit into your current workflow? Which integration point would you like to see first?