Closing old issues on GitHub
In the coming weeks, we will be implementing an automatic closure of old issues on some of our GitHub repos. We’ll be closing issues without any activity for 90 days, with some exceptions based on tags. Our plan is to make sure that old issues that have already been solved (but not closed) or are no longer relevant can be cleaned out and make the issues more manageable.
At the time of writing this blog post, there are 1,656 open issues on the main travis-ci repo. There are some fantastic discussions and reports happening there and we want to keep it that way, but with so many open topics, it’s become impossible to reasonably keep track of everything in there. Bugs that were fixed a long time ago (indirectly or directly) or suggestions that have been implemented are likewise sometimes left open.
Going through everything one by one would be an enormous task, and that’d be time that needed to be taken from work being put into new features and bug fixes. While the other repos have more manageable numbers of issues, we still think that closing out older issues would benefit everyone.
To do this, we’ll be implementing Stale, an app for Probot. Many other large repositories use this particular setup, and we’re confident it’ll help us accomplish this.
If an issue you created or you think is still relevant was closed this way, you can go right ahead and either re-open it or create a new one.
We’ll be applying this automatic closure to the following repositories:
As always, if you have any questions or you have any feedback, feel free to let us know via email: email@example.com, and happy building!