If you’re ever thinking about posting “any updates on this?” in a GitHub issue that hasn’t seen any activity in years: there aren’t any updates on this.
@anderseknert well, yes, but I've seen people not close the issues even though relevant PRs were merged
@alphakomet suggesting that the issue is closed in that case is definitely welcome. But that’s certainly not common in comparison to the number of “any updates” posts.
@anderseknert what's your take on comments like "Still interested so I'd be great if this could be added to the roadmap/sprint planning/milestone scope"?
@alphakomet I like using thumbs up on the original description to show that, as it’s also possible to sort issues by reactions.
But to answer your question, you’re MUCH more likely to have your issue addressed if you follow up that comment with a motivation why it’s important to your use case, and of course what your use case *is*. Also often turns out there’s already a way to solve that using existing options, but there’s no way to tell without that context.