Skip to content

Conversation

@lunny
Copy link
Member

@lunny lunny commented Nov 6, 2020

Copy link
Member

@BetaCat0 BetaCat0 left a comment

Choose a reason for hiding this comment

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

LGTM

@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Nov 6, 2020
@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 Nov 6, 2020
@lafriks lafriks merged commit 35cc82a into master Nov 6, 2020
@lafriks lafriks deleted the revert-13217-comments-on-review-should-have-the-same-sha branch November 6, 2020 07:04
@zeripath
Copy link
Contributor

zeripath commented Nov 6, 2020

This should not have been reverted. The migration should have been fixed.

@lunny
Copy link
Member Author

lunny commented Nov 7, 2020

It's not quick to fix that PR when I found the problem because of different database pagination SQL. Since the PR is only online for several hours, so I think revert is the quickest method to prevent more people to upgrade to that commit.

@6543
Copy link
Member

6543 commented Nov 7, 2020

migrations with raw SQL just need more 👀 on review ...

@go-gitea go-gitea locked and limited conversation to collaborators Dec 14, 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants