--
--
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.
For more options, visit https://groups.google.com/d/optout.
On 22 Jul 2016 15:15, "'Dave Borowitz' via Repo and Gerrit Discussion" <repo-d...@googlegroups.com> wrote:
>
> Your arguments against it are the same ones I would make.
>
> This use case is why we added the feature of ${username} in access control refspecs:
> https://gerrit-documentation.storage.googleapis.com/Documentation/2.12.3/access-control.html#_project_access_control_lists
>
This sounds like there is no permission that allows for create reference from existing commits only via git push.
Seems like it would be a really handy permission. Much easier to allow that while still preventing direct pushes of new un-reviewed commits.
--
Darragh Bailey
"Nothing is foolproof to a sufficiently talented fool" - unknown
But does that allow it via 'git push'? as in if the commit exists on the remote can you create a reference using, git push without allowing new commits to be pushed?
git push origin <commit>:refs/heads/my_new_featureWhere commit is already in a remote reference.