This repository has been archived by the owner on Feb 28, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Repo ranger merged immediately without waiting for passing events #1
Labels
bug
Something isn't working
Comments
mfix22
added a commit
to reporanger/ranger
that referenced
this issue
Jun 26, 2020
@moltar sorry to hear this happened to you, and thank you for reporting it. I had not seen this issue in the past. It does seem to me to be a race condition with GitHub actions, so I am going to add a delay to our response, and push up the fix tonight. Give it another try whenever you have a chance, and let me know if it works. Might need to tweak our delay some more. |
Great use of |
Thank you 🙏 Will try again soon! |
Thanks @moltar! 🙏 |
Seems to work fine now! :) Evidence: https://github.com/ScaleLeap/logger/pull/75 |
@moltar thank you so much for checking! ❤️ |
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
I created a PR using a CLI:
hub pull-request -p -l "merge when passing"
The bot merged my PR immediately, 2 seconds after the PR was created.
I think this might be a race condition, as GitHub Actions did not start yet, and bot thought that everything was done.
Maybe the bot needs to detect checks that haven't started yet, or allow for some grace period before merging?
The text was updated successfully, but these errors were encountered: