My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 2221: Pushing to refs/changes/xxxx on a draft change causes the draft to be published
3 people starred this issue and may be notified of changes. Back to list
Status:  New
Owner:  ----


Sign in to add a comment
 
Project Member Reported by david.pu...@sonymobile.com, Oct 30, 2013
************************************************************
***** NOTE: THIS BUG TRACKER IS FOR GERRIT CODE REVIEW *****
***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, INTERNAL *****
***** ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC.    *****
***** THOSE ISSUE BELONG IN DIFFERENT ISSUE TRACKERS!  *****
************************************************************

Affected Version: 2.8-rc1 and master

What steps will reproduce the problem?
1. Create a draft change with `git push origin HEAD:refs/drafts/master`
2. Amend and push to `refs/changes/xxxx` where xxxx is the change number

What is the expected output? What do you see instead?

Expected that the change is still a draft, but it gets published.

Please provide any additional information below.

I'm not sure if the described behaviour is as intended.

Apr 4, 2014
#1 alon.barlev@gmail.com
the behaviour makes sense as there may be drafts push and then non draft.

what I would like to see is the ability to lock a change to draft mode, so that by mistake a push with non draft cannot be accepted.

this is good to enforce draft mode on change until issues are sorted out, and still allow to delete lots of large changes from history.

Sign in to add a comment

Powered by Google Project Hosting