Hi Team,
Currently we have Gerrit 2.13.2 setup. Is there any way to block push to gerrit code review in case if the working copy is not updated?
--
Regards,
Nachu
--
To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Team,
Currently we have Gerrit 2.13.2 setup. Is there any way to block push to gerrit code review in case if the working copy is not updated?
--
Regards,
Nachu
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
On Wed, Apr 5, 2017 at 4:23 AM, Akshya Nachu <akshya...@gmail.com> wrote:Hi Team,
Currently we have Gerrit 2.13.2 setup. Is there any way to block push to gerrit code review in case if the working copy is not updated?Not with Gerrit means. You may try to script something on the client side.However, even if you enforce this policy, the pushed change will again get outdated as soon as another change is submitted.Maybe you want to use the "Fast Forward Only" submit type.
--
Regards,
Nachu
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.