Hello folks,
We've had a bug to automate adding a comment on Github when there is a new spec patch. I'm going to deny this request.
* The glusterfs-specs repo does not have an issue tracker and does not seem to ever need an issue tracker. We currently limit pre-merge commenting on Github to the repos where you have referenced a commit. That is, on glusterfs repo if you reference a bug on glusterd2, we will not comment on the GD2 issue. This is done to prevent noise on external repos. The commit only becomes relevant to the external repo when it's merged.
* A spec is only a proposal for a change. The spec only makes sense when it's been reviewed and merged. At the point when it's merged, Github will pick it up anyway.
For these reasons, I'm going to close this bug as WONTFIX. If you feel strongly about it, please let me know potential use cases for this behavior.
--
nigelb
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-devel
