Software & DevOpsDone with Devin
Set up weekly changelogs and fix docs from GitHub issues
Neon's docs team has Devin create the weekly changelog from a playbook and open or revise doc PRs from GitHub issues, for repetitive work only.
- What They Did
- Neon's docs team standardized the weekly changelog setup as a Devin Playbook, so they only tell Devin to set up the changelog for this Friday. For GitHub issues, they point Devin at an issue, and it reviews the code, finds the docs that need updating, and creates or revises a PR.
- How It Went
- This helped them work through a backlog of older docs issues without auditing each one by hand. Devin struggled with open-ended tasks, and a bulk term rename needed 20+ manual cleanup commits.
- Worth Knowing
- Keep tasks clearly scoped. Devin failed silently on vague jobs, with no clarifying questions or error signals, so check in on its progress yourself.
Try it yourself with Devin
In my docs repo at [path to repo], read the open GitHub issues labeled [label] and make the doc changes each one asks for, one branch per issue. Also draft this week's changelog from [source, e.g. merged PRs since last Friday] following the format in [example changelog file]. Pause and show me each diff before opening any PRs.