evanchueng / gerrit

Automatically exported from code.google.com/p/gerrit
Apache License 2.0
0 stars 0 forks source link

Abandon several changes at once #616

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Add a possibility to abandon several changes (for example when wrong branch was 
accidentally pushed)

Original issue reported on code.google.com by annu...@gmail.com on 4 Jul 2010 at 1:02

GoogleCodeExporter commented 9 years ago
Could you suggest how to approach this?  A button to abandon an entire branch?  
Where would this button go?  Other approaches?

Original comment by mf...@codeaurora.org on 17 Aug 2010 at 5:21

GoogleCodeExporter commented 9 years ago
My first desire was to check this issues (using stars) and delete them all 
(like in e-mail web interfaces). Button could be at the top or in the bottom of 
list. Delete entire branch may be fine too, but I'm in doubt how to select 
branch - it's easier and less error-prone to select individual issues

Original comment by annu...@gmail.com on 18 Aug 2010 at 6:12

GoogleCodeExporter commented 9 years ago
Using stars might not be the best approach because the star
implies "BCC me on emails about this change".

If we added another checkbox icon just to the left of the
star and had a new concept of "Selected Changes" then
you can check off changes to make them "selected" and
apply a bulk action like abandon (or submit?) to the selection.

To pick a branch, we could support selection by query.  That
is the user enters the query "is:open project:foo topic:bar",
uses a new action to "select all results" and then applies the
bulk action to that selection.

This is also related to issue 51, working with multiple
changes at once.

Original comment by sop@google.com on 19 Aug 2010 at 5:16

GoogleCodeExporter commented 9 years ago

Original comment by sop@google.com on 28 Aug 2010 at 9:53

GoogleCodeExporter commented 9 years ago
Hi,
I see this has not been updated recently. I'm trying to abandon all changes 
from a specific "topic" at once. I'm not sure there is a syntax already for 
that.

My first idea was something like this:

git push origin :refs/for/master/topic-name

As it would be the exact opposite of what was done to create topic-name.

Thanks,

Original comment by apeli...@gmail.com on 10 Dec 2013 at 9:00