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

update git vendor to fix wrong release commit id and add migrations (#6224) #6300

Merged
merged 2 commits into from Mar 12, 2019

Conversation

4 participants
@lunny
Copy link
Member

lunny commented Mar 11, 2019

backport from #6224 but the migrations has not been back port so that user have to fix their old data manually.

  • update git vendor to fix wrong release commit id and add migrations
  • fix count
  • fix migration release
  • fix tests

@lunny lunny added the kind/bug label Mar 11, 2019

@lunny lunny added this to the 1.7.4 milestone Mar 11, 2019

@lafriks

This comment has been minimized.

Copy link
Member

lafriks commented Mar 11, 2019

vendor needs to be updated again

lunny added some commits Mar 11, 2019

update git vendor to fix wrong release commit id and add migrations (#…
…6224)

* update git vendor to fix wrong release commit id and add migrations

* fix count

* fix migration release

* fix tests

@lunny lunny force-pushed the lunny:lunny/fix_release_tag2 branch from 4b6fbf4 to 73aef88 Mar 12, 2019

@GiteaBot GiteaBot added lgtm/done and removed lgtm/need 1 labels Mar 12, 2019

@techknowlogick techknowlogick merged commit d0bbfd8 into go-gitea:release/v1.7 Mar 12, 2019

2 checks passed

approvals/lgtm this commit looks good
continuous-integration/drone/pr the build was successful
Details

@lunny lunny deleted the lunny:lunny/fix_release_tag2 branch Mar 13, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.