https://bugzilla.redhat.com/show_bug.cgi?id=1428032
Bug ID: 1428032 Summary: Update WorkerAnt to post to a github issue as soon as a patch is posted against the same Product: GlusterFS Version: mainline Component: project-infrastructure Assignee: nig...@redhat.com Reporter: srang...@redhat.com CC: b...@gluster.org, gluster-infra@gluster.org Gluster intends to move to github to track features being delivered against the code base. Read the announcement here: http://lists.gluster.org/pipermail/gluster-devel/2017-February/052203.html Specifics of the github process here: https://hackmd.io/s/BkgH8sdtg# Towards the above the following change is requested: ---------------------------------------------------- Update WorkerAnt to post to a github issue as soon as a patch is posted against the same Detect patch posted against an issue using the "{Fixes|Updates} #n" or "{Fixes|Updates} gluster/glusterfs#n" in the commit message Change: https://github.com/gluster/gerrit-hooks/blob/master/patchset-created to update the issue to reflect that a patch is posted against it (just like bugzilla is updated by WorkerAnt) This is required, so that we do not have to wait till a merge of the commit, for the details to appear against the issue This needs to change to pick up commits posted against glusterfs, glusterfs-specs, as these are controlled via gerrit For glusterdocs however, only when the documentation PR is submitted and accepted, will the issue be updated (which is fine) WorkerAnt is used to state what should change, but this request may need another bot or some other means of achieving the same. Hence, do not consider WorkerAnt as the final entity that needs to change. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=bBxIPvO9fI&a=cc_unsubscribe _______________________________________________ Gluster-infra mailing list Gluster-infra@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-infra