Skip to content

A GitHub App built with Probot that automates issue replies for the Rivet software design system.

License

Notifications You must be signed in to change notification settings

indiana-university/rivet-issue-bot

Repository files navigation

Rivet Issue Bot

A GitHub App built with Probot that automates issue replies for the Rivet software design system.

The Rivet issue bot also monitors the rivet-source repo for stale issues and sends a weekly report to rivet@iu.edu.

Automated responses

The Rivet issue bot replies to the creation of new issues and the labeling of existing issues. The text of the bot's replies can be found in dialogue.yml.

New issue created

The Rivet issue bot replies to each new issue that's created. If the issue body is less than the issueBodylengthThreshold defined in index.js, the bot will prompt the issue creator for more information.

Label added to issue

The Rivet issue bot posts a comment each time an issue is tagged with one of the labels listed below. Each of the bot's comments explain why the issue was given a particular label, what the issue's opener can expect to happen next, and where on the Rivet wiki they can learn more.

If the label identifies one of the issue types we automatically close, the bot will close the issue as well.

  • add-on candidate
  • as designed
  • bug
  • discussion
  • duplicate
  • havent forgotten
  • not enough info
  • not reproducible
  • out of scope
  • question
  • request

Stale issue report

Once a week, the Rivet issue bot looks through the rivet-source repo and compiles a list of all stale issues.

An issue is considered stale if there's been no activity on an open issue for more than the number of days defined in the STALE_ISSUE_DAYS_CUTOFF environment variable. By default, the cutoff is 30 days.

About

A GitHub App built with Probot that automates issue replies for the Rivet software design system.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published