This fork supports reminders on the closed issues. However, contrary to the original repo, it has limited support for the reminder prompts and only supports the following format:
/remind [who] to [what] [when]
(e.g.,/remind me to review this PR in 6 hours
)/remind [who] [when] to [what]
(e.g.,/remind @kublaios in 2 days to address the comments
)
Where [when]
is recognized only in the following formats: in|after X minute(s)|hour(s)|day(s)|month(s)|year(s)
Based on the probot reminder bot that no longer works. Now in a 2 part github action form! One action to create the reminder metadata and label. And another to run on a schedule to let you know when your reminder is due.
This action requires the use of agrc/create-reminder-action as well.
Use the /remind
slash command to set a reminder on any comment box on GitHub and you'll get a ping about it again when the reminder is due.
Use any form of /remind me [what] [when]
, such as:
/remind me to deploy on Oct 10
/remind me next Monday to review the requirements
/remind me that the specs on the rotary girder need checked in 6 months
name: 'check reminders'
on:
schedule:
- cron: '0 * * * *'
jobs:
reminder:
runs-on: ubuntu-latest
steps:
- name: check reminders and notify
uses: agrc/reminder-action@v1
GitHub Actions will run the entry point from the action.yml. Packaging assembles the code into one file that can be checked in to Git, enabling fast and reliable execution and preventing the need to check in node_modules.
Actions are run from GitHub repos. Packaging the action will create a packaged action in the dist folder.
-
Semantic version (for major changes, a new v(major) branch is required)
npm version (minor | patch) --no-commit-hooks --no-git-tag-version
-
Run prepare
npm run prepare
-
Since the packaged index.js is run from the dist folder.
git add dist package*.json
-
Commit changes
git commit -m "release: v1.*.*"
-
Use the draft a release workflow on GitHub.
- pick a color + pet name generator with the first letter matching the first letter of the color