Skip to content

Fix .comment-code-cloud not being removed when cancelling new code comment (#11464) #11466

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 2 commits into from
Closed

Fix .comment-code-cloud not being removed when cancelling new code comment (#11464) #11466

wants to merge 2 commits into from

Conversation

lafriks
Copy link
Member

@lafriks lafriks commented May 17, 2020

Backport #11464

@lafriks lafriks added this to the 1.12.0 milestone May 17, 2020
@lafriks lafriks added the skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. label May 17, 2020
@lafriks lafriks changed the base branch from master to release/v1.12 May 17, 2020 20:38
@lafriks lafriks closed this May 17, 2020
@lafriks lafriks removed this from the 1.12.0 milestone May 17, 2020
@lafriks
Copy link
Member Author

lafriks commented May 17, 2020

Damn, there is one more PR in the middle already :]

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label May 17, 2020
@CirnoT CirnoT deleted the code-comment-cancel branch May 17, 2020 20:56
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
@delvh delvh added issue/not-a-bug The reported issue is the intended behavior or the problem is not inside Gitea and removed reviewed/invalid labels Oct 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

No reviews

Assignees

No one assigned

Labels

issue/not-a-bug The reported issue is the intended behavior or the problem is not inside Gitea lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. type/bug

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@lafriks @GiteaBot @delvh @CirnoT