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
I've noticed that many issues on this repository are being automatically closed due to inactivity, not because they are resolved. This practice makes it difficult for users to suggest improvements or report bugs because issues get closed prematurely, leading to lost feedback and unresolved problems.
Whenever I try to suggest a solution or raise a concern, the issue eventually gets closed if there's no activity. Additionally, I’ve found dozens of issues mentioning the same problem, and they are all closed due to inactivity—not because a solution was provided. This system creates a frustrating experience, as valid issues are swept away without resolution or proper acknowledgment.
Please reconsider Auto-Closing Policies
The text was updated successfully, but these errors were encountered:
Hi flutter_file_picker team,
I've noticed that many issues on this repository are being automatically closed due to inactivity, not because they are resolved. This practice makes it difficult for users to suggest improvements or report bugs because issues get closed prematurely, leading to lost feedback and unresolved problems.
Whenever I try to suggest a solution or raise a concern, the issue eventually gets closed if there's no activity. Additionally, I’ve found dozens of issues mentioning the same problem, and they are all closed due to inactivity—not because a solution was provided. This system creates a frustrating experience, as valid issues are swept away without resolution or proper acknowledgment.
Please reconsider Auto-Closing Policies
The text was updated successfully, but these errors were encountered: