When to close an issue

The best time to close an issue is after a pull request is merged that completely solves an issue. However, sometimes that is not possible.

Other possible reasons to close an issue:

• It is a duplicate of another already existing one with no new useful details. Please link the issue to be closed to the (more detailed) older one with a comment. Then close it as a duplicate.
• It is a bug with another piece of software entirely unrelated to pygame-CE - Try to helpfully direct the issue poster to where they might get some help and then close the issue.
• It is a bug with a piece of software related to pygame e.g. SDL - Check to see if the bug is reported on the piece of related software's issue tracker - if it is, see if we can solve it in pygame by updating software, if we still need to wait, or if it is unsolvable. Link to the other issue and then - if it is unsolvable close the issue. If it will be solved later, link to the issue on their tracker and leave the pygame CE one open. If we can solve it soon, link to the issue and hope some kind soul opens a PR to do so. If it has not been reported, ideally report it on the other piece of software's issue tracker and link to the new issue.
• It is not an issue with pygame CE itself, but with the issue writer's lack of knowledge that they could rectify themselves - Please politely close the issue, linking to the documentation if appropriate, or to one of the various community help resources (e.g. Discord, reddit).