Protocol for closing GitHub issues
6 views
Skip to first unread message
Henry Rich
May 10, 2026, 9:59:17 AMMay 10
to forum
If there is a generally accepted way of closing GitHub issues, please
enlighten me. Failing that, I propose the following.
1. When a fix for an issue is pushed to our repo, the maintainer gives
it the 'fixed' label with a comment indicating what release# it will be
fixed in.
2. When a new beta comes out, owners of open issues will close issues
that they verify it properly fixes.
3. A couple of weeks after a release, the maintainer will close any
fixed issue that has not been commented on.
We have just released 9.8.0-beta2, so you should check issues that it
purports to fix. NOTE that some issues are marked as being fixed in the
unreleased 9.8.0-beta3.
Henry Rich
enlighten me. Failing that, I propose the following.
1. When a fix for an issue is pushed to our repo, the maintainer gives
it the 'fixed' label with a comment indicating what release# it will be
fixed in.
2. When a new beta comes out, owners of open issues will close issues
that they verify it properly fixes.
3. A couple of weeks after a release, the maintainer will close any
fixed issue that has not been commented on.
We have just released 9.8.0-beta2, so you should check issues that it
purports to fix. NOTE that some issues are marked as being fixed in the
unreleased 9.8.0-beta3.
Henry Rich
Reply all
Reply to author
Forward
0 new messages