A chatbot answers. Morrow remembers, acts, and waits.See the difference →
All workflows

Product · Overnight

Overnight engineering

Pull requests, failing checks, and ticket status are ready before the team sits down. The standup posts only after you approve it.

Overnight engineering

An updated board and a standup the team can start from.

Pull requestsGitHub
New errorsSentry
SummarizeGitHub
Update the boardJira
Draft standupSlack
PostSlack

Outcome

An updated board and a standup the team can start from.

Tools

Agents

How it works

Step 1Collect

Overnight pull requests and new errors are gathered in one pass.

  • Read merged, open, and failing pull requests on GitHub.
  • Pull new Sentry issues since the last standup.
  • Skip anything already owned and unchanged.
GitHubSentry
Step 2Summarize

Each change is reduced to what shipped, what is stuck, and who owns it.

  • Summarize each pull request in a few lines a teammate can scan.
  • Name the reviewer still blocking a merge.
  • Tie a Sentry issue to the pull request when the stack matches.
Step 3Update

Jira and Linear match what GitHub already shows.

  • Move the linked Jira or Linear issue to the status the code is actually in.
  • Write the pull request link into the ticket.
  • Leave a ticket alone when no one owns it yet, and say so.
Step 4Draft

The standup is written. It does not post yet.

  • Group the note by shipped, stuck, and needs a person.
  • Name the owner on every line.
  • Hold the Slack post until you approve it.
SlackYou approve
Step 5Post

The approved note is the first thing the team reads.

  • Post the standup in the engineering Slack channel.
  • Keep the same note on the record for the next morning.

Run one of these on your stack.

We connect the tools, set the approval, and leave the workflow with your team.

Overnight engineering — Morrow