question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Lock issues that have been closed for awhile

See original GitHub issue

Users occasionally leave comments on issues that have been closed for a long time. These comments usually take one of two forms:

  1. The user believes they are encountering a bug which was purportedly already fixed
  2. The user is expressing support for a feature request which was closed due to lack of interest (or other reasons)

I’ve noticed that in most cases, these comments are not actionable. In case 1, users often don’t provide enough information to triage the new report, so we encourage them to create a new issue. In case 2, we encourage users to create a new issue anyway in order to get more attention to the feature request.

I think we should consider locking issues and PRs that have been closed for a long time (e.g. a month). This might encourage users to create a new issue with more information, rather than appending discussion which is often irrelevant to the original subject of the issue.

Some other open-source repositories that do this:

I like Go’s approach of adding a label to the locked issue to describe why it was locked without spamming everyone with notifications.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:1
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

3reactions
ilyavolodincommented, Jan 10, 2018

I’m not sure this is a good idea. First of all, I think it has a possibility of creating a lot of additional noise. If people can’t post “I just ran into this” in the closed issues, they might create a slew of new issues that we have no resolution for (either because they are non-issues, or because we already decided not to address them). I think it might also disway some people from posting as well. Our rules for creating new issue are pretty strict, and a lot of people will not go through with them. In general, I don’t see people posting on closed issues as a big problem. It’s easy to click through them in the issue tracker (at least for me). All of the above is a personal opinion.

1reaction
not-an-aardvarkcommented, Jan 21, 2018

In the TSC meeting a few days ago, we decided to start locking issues 6 months after they are closed, and to reevaluate how the strategy is working in 2 months.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Door Lock Problems and How to Fix Them | HomeServe USA
Door lock problems are often caused by a malfunctioning lock mechanism or latch assembly, but there are several common reasons why locks ...
Read more >
5 Common Lock Problems and How to Fix Them
Poorly cut keys will always be a problem in locks, which is why it is important to use a reputable locksmith when you...
Read more >
5 Reasons Your Door Won't Close And How To Fix It
When a door won't close, it is due to an issue with the door or the lock. But it will always result in...
Read more >
How Changes In Temperature Affect Locks
One of the most common causes of lock issues is changing weather. Fluctuating temperatures can cause exterior door locks to jam and not...
Read more >
Common Door Lock Problems - I Can't Lock My Door - LockRite
If you're having problems trying to lock your door, your key is stuck or your key is hard to turn in the lock,...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found