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

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

Merged
merged 2 commits into from May 2, 2019

Conversation

@SagePtr
Copy link
Contributor

commented May 2, 2019

Backport #6833

@techknowlogick techknowlogick added this to the 1.8.1 milestone May 2, 2019

@lafriks

This comment has been minimized.

Copy link
Member

commented May 2, 2019

0 changed files? :/

@GiteaBot GiteaBot added the lgtm/need 2 label May 2, 2019

@lafriks

This comment has been minimized.

Copy link
Member

commented May 2, 2019

Could it be that 1.8 is not affected

@SagePtr

This comment has been minimized.

Copy link
Contributor Author

commented May 2, 2019

Whoops, looks like i pushed a wrong branch)

@SagePtr SagePtr force-pushed the SagePtr:issue6832b branch from 22fa6ad to 24d46b0 May 2, 2019

@lafriks

lafriks approved these changes May 2, 2019

@GiteaBot GiteaBot added lgtm/done and removed lgtm/need 2 labels May 2, 2019

@lafriks

This comment has been minimized.

Copy link
Member

commented May 2, 2019

That's better :)

@adelowo

adelowo approved these changes May 2, 2019

@lafriks lafriks merged commit 74eee64 into go-gitea:release/v1.8 May 2, 2019

2 checks passed

approvals/lgtm this commit looks good
continuous-integration/drone/pr Build is passing
Details

@SagePtr SagePtr deleted the SagePtr:issue6832b branch May 2, 2019

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