Flag stale docs
When a published doc has not changed in 90 days, mark it stale and ask its owner to check it.
- When
- A doc goes stale
- Then
- Mark stale and notify the owner
Active14 runs in 30 days
Automations
Rules that keep docs current, so nobody has to remember to.
Active rules
4of 6
2 paused
Runs in 30 days
30
From 4 rules
Busiest rule
14runs
Flag stale docs
Last run
Today
Review reminders
Archive sprint docs
When a sprint ends, move its plan and retro to Sprint Archives.
- When
- A sprint ends
- Then
- Move to Sprint Archives
Active2 runs in 30 daysDraft release notes
When a release ships, start a release note from its merged changes.
- When
- A release ships
- Then
- Create a draft in Release Notes
Active3 runs in 30 daysAnnounce new docs
When a doc is published, post it to the team channel.
- When
- A doc is published
- Then
- Post to the team channel
Paused0 runs in 30 daysReview reminders
Two days before a doc's review date, remind its owner and reviewers.
- When
- A review is due
- Then
- Remind the owner and reviewers
Active11 runs in 30 daysSync API references
When the API repository changes, update the matching reference pages.
- When
- A connected source changes
- Then
- Update API References
Paused0 runs in 30 daysNever run
Runs by rule
30 days
- Flag stale docs14 runs
- Review reminders11 runs
- Draft release notes3 runs
- Archive sprint docs2 runs
- Announce new docs0 runs, paused
- Sync API references0 runs, paused
How automations work
Something happens
A doc passes its review date or goes stale, a sprint ends, a release ships, or a connected tool changes.
The rule does its part
It marks, moves, drafts, or sends a reminder, the way a teammate would have.
Pause it any time
Switch a rule off to stop its next runs. What it already did stays as it is.