Reset requested moves before writing a new move - #957
Merged
Conversation
Debilski
force-pushed
the
feature/reset-requested-moves
branch
from
June 2, 2026 12:43
944b4bb to
7d6bcdf
Compare
Debilski
force-pushed
the
feature/reset-requested-moves
branch
from
June 2, 2026 12:52
7d6bcdf to
0049cdb
Compare
github-actions Bot
pushed a commit
that referenced
this pull request
Jun 3, 2026
Reset requested moves before writing a new move ff3a48e
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Trimming down the
requested_movesdict a little which keeps track of what position a bot requested and whether it was successful. I think the whole requested_moves list can be rethought a little – now that bad moves fail immediately, it does not really capture a lot of info anymore, but I still would like to record that a move was a success, so I keep it for now.