Close issues with status/needs-feedback that were last updated more than a month ago

[yardenshoham]

We will close issues with the label status/needs-feedback if there is no new activity in the past month.

• Closes A new label to close an issue if there are 1 month no response after the label marked. #106

[yardenshoham]

Issues that will get closed:

• Documentation: Specify that you *need* to rename the executable go-gitea/gitea#26240
• error when push image to registry => Container registry go-gitea/gitea#25832
• 500 error after migrating repository and deleting team from old organisation go-gitea/gitea#25700
• User preference to adjust diff colors for color blindness go-gitea/gitea#25680
• Push failed with "Unable to find configuration file" go-gitea/gitea#25633
• Organization permissions go-gitea/gitea#25607
• Clean expire package not clean all go-gitea/gitea#25035
• Container registry windows images go-gitea/gitea#24974
• Glitch in Tags view go-gitea/gitea#24756
• Web index undr gitea go-gitea/gitea#24720
• Branch protection, can still be pushed go-gitea/gitea#24373
• Private attachments go-gitea/gitea#23071
• Compare release with other tagged versions not working go-gitea/gitea#22737
• When Creating an Issue, Attachments that are Added and then Removed are Still Attached go-gitea/gitea#22731
• Why did I not merge to the master/main? It also shows that the branches have been merged go-gitea/gitea#22116
• Restoring a backup: login source already exists [name: OpenLDAP] go-gitea/gitea#21674
• repo collaborator can access all repositories of an organisation go-gitea/gitea#20668
• Source branch reference should probably be user/repo go-gitea/gitea#20408
• Merge a branch into master, then open a new pr with the same branch: still show diff. I expect no diff, as it's already merged. go-gitea/gitea#19878

Issues that will remain open:

• Gitea won't start after upgrade go-gitea/gitea#26946
• GUI - Refresh Custom Files go-gitea/gitea#26925
• Profile Gravatar image won't load go-gitea/gitea#26900
• gitea(v 1.20.3) is not coming up after redis cluster pod ip is changed. go-gitea/gitea#26893
• Queue unexpected type conversion go-gitea/gitea#26843
• LFS file is not remove when branch is removed. go-gitea/gitea#26668
• Chaning Admin Username does not reflect the change at repositories Panel.  go-gitea/gitea#26603
• After upgrade, can't create repo in existing org go-gitea/gitea#26482
• OIDC group mappings don't apply at registration go-gitea/gitea#26415
• Check storage readiness and show meaningful error message when DB is busy go-gitea/gitea#26011
• Gitea container register ask auth for all users except Administrators on public registry go-gitea/gitea#25908

[lunny]

Should we need authors' response or anyone's response will be OK?

[yardenshoham]

The check is for any update to the issue

[lunny]

And take a look at go-gitea/gitea#23071 , @delvh has commented after the label added?

[yardenshoham]

Yes, but there was no activity. Do you prefer it will stay open even if there is no activity?

[lunny]

Yes, but there was no activity. Do you prefer it will stay open even if there is no activity?

For that issue, I think it should be kept open because it's a feature. Maybe we should add another label bug.

That is if it's a bug report but there is a needs-feedback label but there is no response from author for a month?

[yardenshoham]

I think we should simply remove status/needs-feedback from issues that should remain open...

[lunny]

Looks most closings are right.

[jolheiser]

This seems somewhat unfriendly imo.

This issue has the status/needs-feedback label and hasn't received activity in a month or more, so it is being closed. If you feel this was in error (misplaced label or otherwise), please let us know so we can re-evaluate. If you are not the original author, consider opening a new issue linking to this one instead.

Or something along those lines? The current wording seems very strong to me.

[yardenshoham]

Sure, send a PR to change it

[jolheiser]

I think we should simply remove status/needs-feedback from issues that should remain open...

I agree with this, however as humans I think it will be imperfect, so I think (as in my review) that perhaps the wording could be a little softer in the event an issue is closed in error.

[KN4CK3R]

I don't like that. There are only a few issues with that label, not really a place for automation.

[yardenshoham]

@lunny requested it, so I implemented it. If it causes trouble I don't mind reverting this PR

[jolheiser]

I think it could be feasible, however currently our usage of the label is probably inconsistent.

[lunny]

I have checked all closed issues, I think most of them are expected. It can give us a reminder the author has no response for a report.

[wxiaoguang]

The real problem is that not enough people are reviewing the issue list regularly. So only a few "needs-feedback" would be added.