gitea
gitea copied to clipboard
go-gitea
[Feature] Auto-lock PR Conversations When Merged
Feature Description
I think it would be helpful if repos had a setting to automatically lock a conversation when an issue is closed and/or PR is merged.
Related to: https://github.com/go-gitea/gitea/issues/20012
Screenshots
No response
Wouldn't it be better to let a CI do that? Then we don't have a weird edge case that is only sometimes wanted in our core while still providing the functionality… As far as I know, the CI currently proposed should (later on) be able to do that (see #21937)
Wouldn't it be better to let a CI do that? Then we don't have a weird edge case that is only sometimes wanted in our core while still providing the functionality… As far as I know, the CI currently proposed should (later on) be able to do that (see #21937)
Yeah, I appreciate your point, but CI seems like overkill for this if a user isn't already running CI for something else (also, is there a webhook for issues closed or would the CI job it have to poll each open issue?). It seems like what you suggest is the strategy GitHub has taken, as there doesn't seem to be a feature like this built in. From a UX perspective, it seems like like a nice compliment to auto-merge.
If this really is a niche feature that a majority of users don't want/need, I agree it should go to CI. If a reasonable number of folks want this it would be nice to build into the UI. I'll post in discord and see if other people would like this feature, and if there's not much traction in a week then I'm perfectly happy closing this.
also, is there a webhook for issues closed or would the CI job it have to poll each open issue?
Yes-ish, the base issues covers "Issue opened, closed, reopened, or edited."
The job would need to check if it was closed specifically, but the event would come across.
Wouldn't it be better to let a CI do that? Then we don't have a weird edge case that is only sometimes wanted in our core while still providing the functionality… As far as I know, the CI currently proposed should (later on) be able to do that (see #21937)
Yeah, I appreciate your point, but CI seems like overkill for this if a user isn't already running CI for something else (also, is there a webhook for issues closed or would the CI job it have to poll each open issue?). It seems like what you suggest is the strategy GitHub has taken, as there doesn't seem to be a feature like this built in. From a UX perspective, it seems like like a nice compliment to auto-merge.
If this really is a niche feature that a majority of users don't want/need, I agree it should go to CI. If a reasonable number of folks want this it would be nice to build into the UI. I'll post in discord and see if other people would like this feature, and if there's not much traction in a week then I'm perfectly happy closing this.
That Action could be reused when Gitea Actions PR merged.
