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 have searched open and closed issues for duplicates
I am submitting a bug report for existing functionality that does not work as intended
This isn't a feature request or a discussion topic
Bug description
This is a bug of this Github repository not of the Signal App.
In the search of a missing feature (this one but not that relevant) the forum linked to a closed issues and a closed PR in the repo. Both are closed while not getting attention.
In #5030 the author checked for a fix for multiple versions and commented on the issue that version x still did not fix it. After a while he stopped. Apparently this is what this repository expects to regularly say "still an issue" because after stopping, stale bot commented with "Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs." and marked it as wontfix. Only one other person commented as well and it was not someone from the project. The author commented with "still relevant" on this kind of comment multiple times (as did other people). But in the end, after one more "Is this still relevant?" message a week went by with no one reacting and the issue was permanently closed.
This super toxic to anyone taking the time to interact with your project. If you don't care about issues, fine, do not allow people to open issues. Using stale bot to close support requests or bugs where there is more information needed but the author has gone missing, also fine. But please don't insult people's time by just letting a bot close a ticket a human has never even layed eyes on.
Steps to reproduce
Report an issue
Get no response and the issue persists
-> Stale bot comments on the issue that it will close it and marks it as wontfix
Not reacting to it for one week (this is the span of a holiday, a hospital visit, or just life happening)
-> Stale bot closes issue
Actual result: Issue gets closed with no way to reopen it
Expected result: Do not run stale bot on issues that are not marked in a certain way that warrants closing
Screenshots
Device info
Not relevant
Link to debug log
Not relevant
The text was updated successfully, but these errors were encountered:
Bug description
This is a bug of this Github repository not of the Signal App.
In the search of a missing feature (this one but not that relevant) the forum linked to a closed issues and a closed PR in the repo. Both are closed while not getting attention.
In #5030 the author checked for a fix for multiple versions and commented on the issue that version x still did not fix it. After a while he stopped. Apparently this is what this repository expects to regularly say "still an issue" because after stopping, stale bot commented with "Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs." and marked it as wontfix. Only one other person commented as well and it was not someone from the project. The author commented with "still relevant" on this kind of comment multiple times (as did other people). But in the end, after one more "Is this still relevant?" message a week went by with no one reacting and the issue was permanently closed.
This super toxic to anyone taking the time to interact with your project. If you don't care about issues, fine, do not allow people to open issues. Using stale bot to close support requests or bugs where there is more information needed but the author has gone missing, also fine. But please don't insult people's time by just letting a bot close a ticket a human has never even layed eyes on.
Steps to reproduce
Actual result: Issue gets closed with no way to reopen it
Expected result: Do not run stale bot on issues that are not marked in a certain way that warrants closing
Screenshots
Device info
Not relevant
Link to debug log
Not relevant
The text was updated successfully, but these errors were encountered: