Request for approval: deploying dlang.org on merge

[Vladimir Panteleev via Digitalmars-d]

On Thursday, 26 May 2016 at 16:38:16 UTC, Andrei Alexandrescu 
wrote:
> If Vladimir is okay with auto-deployment I'm okay too. Move 
> fast!

This is now live. (Perhaps it should be posted in Announce?)

> The only question is, how do we avoid cases in which a 
> deployment breaks something important? -- Andrei

1. Check the documentation tester results before merging 
anything. This also applies to other components (Phobos, 
Druntime, DMD) though most changes there are unlikely to break 
things.
2. If something breaks, make and merge a PR which reverts or 
fixes it. Pushing directly to master would also work, but 
wouldn't make a big difference in practice.
3. If that doesn't work, people with access can always ssh to 
dlang at k3.1azy.net or dlang.org to fix things by hand.