Autopilot emails the people told about a project when a merged pull request has updates: what needs your approval, what goes out by itself and when, and what it did already. You can act on most updates straight from the email.
Who's told is set per project by its owners, under Who's told in Settings → Autopilot: owners, admins if Admins too is ticked, and the teammates ticked there. See Set up Autopilot.
Choose when you hear
Each person chooses for themselves. Open the menu at the bottom of the sidebar, choose Account settings, and pick under Autopilot's email. Your choice saves as you pick it, and covers every project that tells you.
As they happen (the default): an email when a merged pull request has updates. Pull requests merged within ten minutes of each other come in one email.
A daily digest: one email each morning, per project, with everything still waiting for your approval, and none on a day with nothing. It comes at 8 am in your browser's time zone when you picked it, which the option names. If you move to another time zone, it says "Pick it again to use …": choose A daily digest again. Projects with Autopilot off send no digest.
Off: no emails.
If you own a project, you still get an email whatever you picked when something your users see goes out by itself, or is about to. So nothing reaches your users without an owner knowing.
When Autopilot reads a pull request again, the people told hear about it again.
What the email says
It comes from "Tuti Autopilot". The subject puts what needs you first, such as "1 needs you, 1 goes out in 24 hours · Add CSV export to reports", or "3 pull requests" when there are several. A digest's subject says what still needs you, such as "3 still need you · 2 pull requests".
Tiles at the top count the updates in each list.
Each pull request has what changed for users and Review in Tuti →, which opens its activity page.
The updates come in up to four lists: Needs your approval, Auto-updating (going out by itself, and when), Published already (went out by itself before the email went) and Only your team sees (drafts Autopilot wrote by itself).
Each update says what it is, what it does, and how sure Autopilot is, such as "93% sure". An article edit shows its changed lines, up to 8, and a progress update or completion shows its comment.
The email shows 5 updates at most. Past those, +N more in Tuti opens Autopilot.
The footer's Choose when you hear from it opens your Account settings.
Act from the email
Approve approves that update as the email shows it. An article edit is published; completing a post emails the people who asked.
Edit opens the post's or article's review in Autopilot, to change it or look closer before you decide.
Publish now sends a pull request's auto-updating updates out at once. Stop keeps them from going out by themselves: they wait for your team. With several pull requests in the email, the buttons name which one, like Stop #418, or by its full name, like Stop lumenhq/lumen-app#418, when two of them from different repositories share a number.
Some updates only have Edit, because approving them from the email could do more than it shows:
an update that's out of date, or that a teammate stopped;
a progress update with no comment, or a comment too long to post;
an article edit while the article also has a teammate's unpublished edit or another pull request's edit;
an edit to a draft, which you approve on its review and which stays in the draft (the email says "Keeps this edit in the draft only your team sees").
The buttons work for the person the email was sent to, for 7 days. If you're signed out, you sign in first and then it's done. Anyone else, or a link that's too old, gets the review or the pull request's activity page instead, and nothing is done.
After a click, Tuti opens the review (for Publish now and Stop, the pull request's activity page) and says what happened, such as "Approved: … Undo it from its pull request's chip." If someone decided first, it says who and when. If the update changed since the email, nothing is approved, and the page shows it as it is now.
Verify's emails
Owners who chose As they happen also get an email when Verify finds an article out of date and writes a fix, and one when a Verify all ends with fixes waiting. The daily digest doesn't include them, but the fixes wait in Autopilot with the rest.