Le lundi 23 novembre 2015 à 16:41 +0530, Kaushal M a écrit : > On Mon, Nov 23, 2015 at 4:26 PM, Michael Scherer <[email protected]> wrote: > > > > Le jeudi 29 octobre 2015 à 11:24 +0000, Niels de Vos a écrit : > > > Humble Chirammal <hchiramm@...> writes: > > > > > > > > > > > > Hi, > > > > FYI, > > > > It seems that, https://github.com/gluster/glusterfs code > > > > repo has not synced from gerrit for some time and the last commit ( > > > > 51632e1eec3ff88d19867dc8d266068dd7db432a) > > > > recorded on Sep 10 . > > > > Does any one know, why the gerrit plugin is broken? -- > > > > > > I've now manually synced the glusterfs repo on GitHub with the current > > > state > > > from Gerrit. If the automatic sync takes time to get configured/setup > > > again, we > > > might need to do this on regular basis? Anyway, ping me if it needs to be > > > done > > > again (not for each commit though!). > > > > One solution is to just add a ssh key on the repo, it can be found in > > the settings. > > > > I always thought that this was for things like automated deployment > and mirroring. I didn't know it worked for pushing to the repo.
There is a checkbox for write access when adding a key: "Can this key be used to push to this repository? Deploy keys always have pull access. " I suspect they might have added the feature silently some time ago, and people do not use it often enough to know about it (I personally found it today.. ) -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gluster-infra mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-infra
