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.

Sign up for GitHub

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

Jump to bottom

Double merge in quick succession #54

Closed
silverwind opened this issue Apr 23, 2023 · 4 comments
Closed

Double merge in quick succession #54

silverwind opened this issue Apr 23, 2023 · 4 comments

Comments

@silverwind
Copy link
Collaborator

go-gitea/gitea#22175

These were pretty much back-to-back:

image
@yardenshoham
Copy link
Collaborator

Possibly because we trigger it on push and on pull_request labeling

@silverwind
Copy link
Collaborator Author

silverwind commented Apr 23, 2023 •
edited
Loading

This was a bit of an odd case. I added a . comment to satisfy the lgtm bot, but then another PR was landed into main pretty much at the same time. I guess it was bad timing.

@yardenshoham
Copy link
Collaborator

So close?

@silverwind
Copy link
Collaborator Author

I guess. Let's see how it goes with new lgtm bot then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@silverwind @yardenshoham