Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport: add reviewers as participants #8124

Merged

Conversation

guillep2k
Copy link
Member

Backport for #8121

This PR add reviewers to the list of participants of an issue.

Currently, only users that add a plain comment (CommentTypeComment) are counted as participants. If a user adds a review/request changes (CommentTypeReview or CommentTypeCode) they are not considered participants.

Fixes #8122

@lafriks lafriks added this to the 1.9.4 milestone Sep 7, 2019
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Sep 7, 2019
@guillep2k
Copy link
Member Author

guillep2k commented Sep 7, 2019

@lafriks this should have milestone 1.9.4 - the other one should have 1.10.0
Don't mind me. 😁

@lafriks
Copy link
Member

lafriks commented Sep 7, 2019

I already set so

@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Sep 7, 2019
@lunny lunny added the status/blocked This PR cannot be merged yet, i.e. because it depends on another unmerged PR label Sep 7, 2019
lunny
lunny previously requested changes Sep 7, 2019
Copy link
Member

@lunny lunny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

blocked until v1.9.3 released

@lunny lunny removed the status/blocked This PR cannot be merged yet, i.e. because it depends on another unmerged PR label Sep 8, 2019
@guillep2k
Copy link
Member Author

I guess the build failing is a CI problem?

@techknowlogick
Copy link
Member

I think the swagger/gomod changes that were made to master, may need to be backported first.

cc: @sapk

@lunny
Copy link
Member

lunny commented Sep 9, 2019

That's a make vendor failed not swagger.

@techknowlogick
Copy link
Member

@lunny you can see that swagger command modifies go.mod, which causes make vendor to fail.

@guillep2k guillep2k mentioned this pull request Sep 12, 2019
@guillep2k
Copy link
Member Author

I think this needs #8087 backported.

@sapk
Copy link
Member

sapk commented Sep 12, 2019

@guillep2k backport is done.

@guillep2k
Copy link
Member Author

Make LG-TM work

@techknowlogick techknowlogick dismissed lunny’s stale review September 12, 2019 21:52

1.9.3 has been released

@techknowlogick techknowlogick merged commit b228d22 into go-gitea:release/v1.9 Sep 12, 2019
@guillep2k guillep2k deleted the fix-issue-participants-v1.9 branch September 12, 2019 23:31
if !isAdded && !issue.IsPoster(comment.Poster.ID) {
participants = append(participants, comment.Poster)
}
participants = addParticipant(comment.Poster, participants)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The issue Poster should not be added to participants according before logic.

if !issue.IsPoster(comment.Poster.ID) {
    participants = addParticipant(comment.Poster, participants)
}

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants