You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With 17 PRs and 2 years without anything on the stable, is this repo dead?
I've just had a perfectly fine and well-reasoned feature request #422 considered stale eventually because no one had paid attention to the fact that I've solved my own issue by a simple Pull Request complete with specs. It would have taken 5 minutes to review.
I must say I do find it a bit disrespectful to apply automation on a poorly maintained repo and just auto-disregard contributions. Very often we all maintain some libraries and lack time, but we shouldn't slap automation on it and leave it running rogue closing valid code contributions.
The text was updated successfully, but these errors were encountered:
Hello @ain, this repository is not dead yet, just got overlooked due to lack of pings from contributors, signalling either stability of last release or drop in usage of this plugin entirely.
Regarding the closing of your pull request, GitHub UI has no indication that the PR was closed by automation from maintainers' side.
You are free to resubmit a fresh pull request onto the current master branch. Though, given the changes to the twitter platform over the years, I'd like to see a reference to support your proposed change.
With 17 PRs and 2 years without anything on the stable, is this repo dead?
I've just had a perfectly fine and well-reasoned feature request #422 considered
stale
eventually because no one had paid attention to the fact that I've solved my own issue by a simple Pull Request complete with specs. It would have taken 5 minutes to review.I must say I do find it a bit disrespectful to apply automation on a poorly maintained repo and just auto-disregard contributions. Very often we all maintain some libraries and lack time, but we shouldn't slap automation on it and leave it running rogue closing valid code contributions.
The text was updated successfully, but these errors were encountered: