Excessive commits that came from syncing your branches with the upstream one made their way into this PR; it's probably best to make a fresh fork of this repo, keep the upstream master intact (for upstream pulls) and making a new branch for every change you're making; that way you can always pull the latest master updates and branch from that to make sure the PRs will be always ready to merge)
I've cherry-picked the commit you've made into the master branch, so it's included in the repo; I'll close this PR without merging for now, but the changes are accepted and merged into the project
Excessive commits that came from syncing your branches with the upstream one made their way into this PR; it's probably best to make a fresh fork of this repo, keep the upstream master intact (for upstream pulls) and making a new branch for every change you're making; that way you can always pull the latest master updates and branch from that to make sure the PRs will be always ready to merge)
I've cherry-picked the commit you've made into the master branch, so it's included in the repo; I'll close this PR without merging for now, but the changes are accepted and merged into the project
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A bit of tweaking in the dictionary.
Excessive commits that came from syncing your branches with the upstream one made their way into this PR; it's probably best to make a fresh fork of this repo, keep the upstream master intact (for upstream pulls) and making a new branch for every change you're making; that way you can always pull the latest master updates and branch from that to make sure the PRs will be always ready to merge)
I've cherry-picked the commit you've made into the master branch, so it's included in the repo; I'll close this PR without merging for now, but the changes are accepted and merged into the project
Pull request closed