Skip to content

Backport: Fix double-generation of scratch token (#6833) #6835

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

Merged
merged 2 commits into from
May 2, 2019

Conversation

SagePtr
Copy link
Contributor

@SagePtr SagePtr commented May 2, 2019

Backport #6833

@techknowlogick techknowlogick added this to the 1.8.1 milestone May 2, 2019
@lafriks
Copy link
Member

lafriks commented May 2, 2019

0 changed files? :/

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label May 2, 2019
@lafriks
Copy link
Member

lafriks commented May 2, 2019

Could it be that 1.8 is not affected

@SagePtr
Copy link
Contributor Author

SagePtr commented May 2, 2019

Whoops, looks like i pushed a wrong branch)

@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels May 2, 2019
@lafriks
Copy link
Member

lafriks commented May 2, 2019

That's better :)

@lafriks lafriks merged commit 74eee64 into go-gitea:release/v1.8 May 2, 2019
@SagePtr SagePtr deleted the issue6832b branch May 2, 2019 21:37
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 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