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

Fix upgrade failed after ever rollback #1197

Merged
merged 1 commit into from
Mar 11, 2017

Conversation

lunny
Copy link
Member

@lunny lunny commented Mar 10, 2017

backport from #1194

* fix upgrade failed after rollback

* fix upgrade failed after rollback

* fix possible upgrade twice fail after rollback
@lunny lunny added the type/enhancement An improvement of existing functionality label Mar 10, 2017
@lunny lunny added this to the 1.1.1 milestone Mar 10, 2017
@andreynering
Copy link
Contributor

LGTM

@tboerger tboerger added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Mar 10, 2017
@strk
Copy link
Member

strk commented Mar 11, 2017

LGTM

@tboerger tboerger 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 Mar 11, 2017
@lunny lunny merged commit fac75b8 into go-gitea:release/v1.1 Mar 11, 2017
@lunny lunny deleted the lunny/fix_rollback_upgrade1 branch March 11, 2017 09:01
ethantkoenig pushed a commit to ethantkoenig/gitea that referenced this pull request Apr 29, 2017
* fix upgrade failed after rollback

* fix upgrade failed after rollback

* fix possible upgrade twice fail after rollback
@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 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/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants