Merge release 2.1.2 into master #867
Conversation
We should not recommend an exact match on 2.0
Fix the installation instruction
|
Appveyor failure is unrelated to this PR, would override. @Ocramius not sure how to proceed with the requirement of having the PR up-to-date with the base branch: that kinda defeats the purpose of doing these merge-ups. Shall we disable that protected branch rule in our repos? |
|
I don't think these merge-up branches will ever be mergeable via UI anyway |
With branch protection enabled, they can only be merged via UI since we can't push directly to other branches. Hence the idea to disable the up-to-date rule. I agree that they will almost never be mergeable without manual work, but that's also the reason why we decided to create PRs from intermediate branches instead of merging directly in the tool. |
Single backslash in double quotes causes malformed YAML error
Escape backslash in YAML example
* 2.1.x: Escape backslash in YAML example Fix the installation instruction
Release 2.1.2
2.1.2
Documentation