4 ms·
What we do is to lock closed issues after a certain time without activity (currently a year). The idea is if it's been closed that long, a new issue should be
by faho 5y ago
What we do is to lock closed issues after a certain time without activity (currently a year).
The idea is if it's been closed that long, a new issue should be filed so you get the context refreshed, and any patch for the original problem would also (most likely) have been in a release already, so it deserves a new issue so we can e.g. link to it in the release notes.
The closing part is all manual, tho.
- cxr 5y agoThe only reason to lock things would be because your userbase can't be trusted to behave responsibly—which, granted, is exactly the expectation of the average GitHub user. In a well-run project, the bugtracker is part of the project's digital memory. This means that the appropriate thing is to cross-link the new bug and the old bug. Not doing so—or being unable to do so because the original bug was locked—makes triage and archaeology needlessly difficult. Say hello to selection pressure: you drive away the most valuable collaborators and are left with the ones that you're spending all your time trying to protect yourself against.
- deleted 5y ago[deleted]