Closed johnnychen94 closed 3 years ago
Since GitHub chose to disable cron jobs after 30/60 days of inactivity, TagBot took an alternative way to work things out, i.e., via issue comment #82. We can safely unsubscribe from #82 because it's specifically for our TagBot CI.
Since GitHub chose to disable cron jobs after 30/60 days of inactivity, TagBot took an alternative way to work things out, i.e., via issue comment #82. We can safely unsubscribe from #82 because it's specifically for our TagBot CI.