Skip to content

Conversation

@stickz
Copy link
Contributor

@stickz stickz commented Mar 7, 2020

This commit allows the user to have a consistent minimum number of maps in the vote, regardless how many previous maps are excluded. It also improves the handling of the situation, when the number of previous maps to exclude is set higher than the number of available maps. Instead of excluding no previous maps, it will exclude until the minimum include count is reached.

This commit allows the user to have a consistent number minimum number of maps in the vote, regardless how many previous maps are excluded. It also improves the handling of the situation, when the number is previous maps to exclude is set higher than the number of available maps. Instead of excluding no previous maps, it will exclude until there's a configurable number of minimum options left.
@stickz
Copy link
Contributor Author

stickz commented Mar 7, 2020

Tested and ready to be merged. The only bug I came across was a separate issue related to PR #1197.

@KyleSanderson
Copy link
Member

@stickz can you rebase?

@stickz
Copy link
Contributor Author

stickz commented Aug 9, 2020

@KyleSanderson re-based in pull request #1333.

@stickz stickz closed this Aug 9, 2020
@peace-maker
Copy link
Member

You don't need to open a new pull request for a rebase. You can rebase your branch onto master and force-push to update this PR.

@KyleSanderson
Copy link
Member

indeed, thanks @peace-maker for calling that out. @stickz why does this keep happening?

@stickz
Copy link
Contributor Author

stickz commented Aug 13, 2020

Sorry, not very experienced with GitHub. The last time I tried to resolve a file conflict it merged 200 files into my pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants