Top 10 tips for project maintainers
summary
Ten concrete maintainer tactics: enable scheduled reminders to ping Slack when PRs need review; use multi-line suggested changes to accept fixes inline instead of cloning; automate labeling and front‑page selection with a five‑line GitHub Script snippet and full CI via GitHub Actions (used to validate every submission in the March hackathon); wire Sponsor webhooks with the open source sponsor‑functions repo; grant a triage role to offload issue triage; enable security advisories and CVEs — GitHub hosts ~50 million developers and a public advisory database.
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:4350 million My job is to advocate for your experience on GitHub.
- 3:09Features! GitHub has been listening and shipping!
- 3:51Feature Savage Remix (feat. Beyoncé)
- 4:22As a project maintainer I would like to know ways to make my job easier. (user story)
- 4:43Top 10 tips for project maintainers
- 5:49Multi-Line Suggested Changes
- 6:30GitHub Actions w/ github-script
- 7:49GitHub Sponsors Webhooks.
- 8:50Saved Replies
- 9:06Triage Role
- 10:19Code Search Tips
- 11:44Honorable Mentions
- 12:21The New Notifications Dashboard + Mobile
- 13:07RFC Discussions
- 13:18RFCs in issues
- 13:44Security Advisories and CVES
- 14:44Create Community
- 15:07As a project maintainer I would like to know ways to make my job easier. (feature complete)
related talks
35mFrom Storming to Performing: Growing Your Project's Contributor Experience
27mManaging A Healthy GitHub Community
20mImprove project usability and reduce friction
29mDon't Be A Hero: Sustainable Open Source
28mPull Requests: Merging good practices into your project
09mMaintaining the Maintainers
50mSustainable package maintenance models
22mYour Open Source Repo Needs A Project Manager