Fix # in comments

• GitHub now parses #n in comments even if they are inside backticks, so we had to update the comment "your PR is #n in the queue" to avoid GitHub interpreting that #n as a link to a Pull Request.
• queue textual status (when accessing bot URL in a browser) is now more readable

JSON Logger for Logz.io

• logs are now using JSON output format to be parsed by our Logz.io instance
• MINIMUM_LOG_LEVEL can be used to filter the logs by level (defaults to "INFO")

Swift 5 & Fixing Tests

• Migrate the bot to Swift 5 and latest RAF
• Bug fix: prevent Mergebot from commenting after a PR has been closed
• Fix tests on Linux

Fix race condition between pending checks and checking commit status

• [IOSP-436] Check for any pending checks before integrating clean PR

Fix MergeService immediately triggering on PR creation

• Changes in 0.12.1 introduced a bug in which every time you create a new PR targeting a branch for which there wasn't a merge queue yet, the PR was immediately added to the new queue (upon queue creation) and scheduled for merging, even if that PR didn't have the integration label yet.
• This release also fixes the WallEView client app to now handle multiple queues.

Parallel Merge Queues

Wall-E now handles multiple parallel merge queues, one per target branch, to be able to merge both develop and release-targeting PRs in parallel.

0.11.2

return queue status as json (#40)

Allow status checks timout to be set via env var

0.11.1

0.11.0

Include a route to inform about the current state of the bot (#36)

0.10.3

Using the main scheduler leads to a deadlock (#35)