Menu

GitHub Reminders Without a Database: Where the Reliability Guarantees Stop
📰

GitHub Reminders Without a Database: Where the Reliability Guarantees Stop

DEV Community: github·Christian Serrano·14 days ago
#AHX2UC2V
#devtogithub#technology#devto#dev#github
Reading 0:00
15s threshold

Many developer tools start with a simple need and grow into an unnecessary service: another database, another scheduler, another account, and a recurring bill.

At Caivra Tech LLC we built GitHub Reminders , a free, MIT-licensed GitHub Action for reminders in issue and pull-request discussions. It uses GitHub comments for persistence and GitHub Actions for scheduled delivery rather than introducing a hosted backend.

This article explains the implementation trade-off—and why we explicitly do not promise exactly-once reminders.

Project and installation instructions: https://github.com/caivra-tech/GitHub-reminders

How it works

A collaborator leaves a command in an issue or PR:

/remind in 7 days Revisit this before deleting the branch /remind in 3 hours Check CI again /reminders

Enter fullscreen mode

Exit fullscreen mode

The configured issue_comment workflow processes the command. A successful creation produces a bot confirmation with a versioned hidden marker containing reminder metadata.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.