3

Based on the response to Migrating a question deleted a comment, comments regarding migration should be removed after migrating.

The following post contains a situation where the comment was not removed, thus required a flag as "no longer needed".

As of the time of this post, the example can be found here: Is it a good practice to add code on an existing class with thousands of lines when adding a new feature in a legacy Java project?

I tagged bug due to the intended behavior mentioned in the first linked post.

Improve this question
2
  • 7
    That's just a custom comment that happens to not match the regex pattern that auto-deletes such comments. Sometimes that happens. We can't automatically catch everything.
    – animuson StaffMod
    Commented Sep 24, 2019 at 3:16
  • 1
    Also, flagging the comment as no longer needed will most likely result in deletion quick enough. Well anyways the entire Q appears deleted now, so that solved itself.
    – Luuklag
    Commented Sep 24, 2019 at 6:47

1 Answer 1

Reset to default
1

I've seen this happen quite a bit, especially when people write up custom comments indicating a question is a duplicate. What happens is the regex used to clean up the comments after a closure doesn't pick up on some comments and thus they get left. Generally, any of the auto-generated comments get picked up in my experience and the issue is more when a user writes their own.

Generally, I would expect the regex for this is written in such a way that minimises incorrect deletion of comments, so it certainly won't be able to pick up everything.

Doing what you did and flagging as No Longer Needed is the correct option for these types of comments.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .