Skip to content

Conversation

@ethantkoenig
Copy link
Member

Fix oversight from #1766

@appleboy
Copy link
Member

LGTM

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

lunny commented May 24, 2017

LGTM, but it's strange why the CI reported build success?

@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 May 24, 2017
@lunny lunny added this to the 1.2.0 milestone May 24, 2017
@lunny lunny added the type/bug label May 24, 2017
@ethantkoenig
Copy link
Member Author

@lunny Usages of the old variable name had been added to master between when the PR CI ran and when the PR was merged into master.

@pgaskin
Copy link
Contributor

pgaskin commented May 24, 2017

LGTM, even though it's already done 😄

@lunny
Copy link
Member

lunny commented May 24, 2017

@ethantkoenig if another PR merged, the CI should be restarted again?

@appleboy
Copy link
Member

@lunny The CI only build master branch if PR merged.

@ethantkoenig
Copy link
Member Author

ethantkoenig commented May 24, 2017

@lunny No, that would flood Drone (we already have a problem with CI jobs getting queued up)

@appleboy appleboy merged commit ff2464c into go-gitea:master May 24, 2017
@ethantkoenig ethantkoenig deleted the rename_fix branch May 29, 2017 14:34
@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/bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants