The bug occurs when the following series of events happens:

• User has at least 2 machines and settings sync is on
• User updates GHPR to the May release on one machine
• 2 settings migrations happen to githubPullRequests.queries, in this order:
  • existing queries that don't specify a repo: have that added
  • The default "Local PRs" and "All Open" queries are added
• The user now has these additional two values in their githubPullRequests.queries settings

    {
      "label": "Local Pull Request Branches",
      "query": "default"
    },
    {
      "label": "All Open",
      "query": "default"
    }

• On the second machine, settings sync kicks in, and syncs down those new settings values
• On the second machine, the users updates GHPR to the May release
• The same migration happens, but there's a flaw
  • existing queries that don't specify a repo: have that added. THIS IS A PROBLEM because the default query values don't have repo:. So those two queries have repo: added. This is already not great, as those queries won't work properly now.
  • the second migration kicks in to add the default queries. Because the two default queries now don't just have default as their value, they get re-added.
• Now the user has two duplicate query labels in githubPullRequests.queries.

The fix: in the first migration, don't add repo: to the two default queries.