My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1986: Don't monitor certain branches (configurable option)
2 people starred this issue and may be notified of changes. Back to list
Status:  New
Owner:  ----


Sign in to add a comment
 
Reported by mat...@gmail.com, Jul 1, 2013
As soon as Gerrit knows about a change on any branch, it can't be pushed as a new change to another, reviewed branch.

Example:
push 3 changes to "tmp/mybranch"
push the same 3 changes to "refs/for/master"
Gerrit will say "No new changes"

The %base feature can be used to make new changes out of this. But still the review can't be enforced for this branch. A user could "squash" the last 2 commits and with a push to refs/for/master also the first commit comes into master (after the squashed commit is submitted).

To offer a kind of playground or backup branch, it would be good to offer an option (per project) to exclude certain branches from the change tracking, e.g. "tmp/*"


Aug 7, 2015
#1 sdram...@gmail.com
If a patchset with change id pushed to gerrit without code review by developer for feature branch, later we are not able to review those commits(patchsets). 
 
Example Scenario:
Developer doesn't want to hold his changes on his local machine for so long. So developer wants to push the changes to gerrit as a backup.

Once the feature is ready, now the developer merge the changes with release branch but now gerrit is not allowing those commits for review.

When this issue will be fixed?   
Sign in to add a comment

Powered by Google Project Hosting