Open jovo opened 8 years ago
I don't understand the use case well.
Can you explain in more detail in what does the weekly code review consist of, and why you need an issue for it?
Do you want some kind of periodic reminder / issue?
Hey Jovo, same issue. Found an answer yet at some other place?
sorry, the use case is that each week i create an issue that is essentially identical to last week's issue.
similarly, i assign it a milestone, which i have to create each week, because i want weekly milestones for our weekly sprints.
so, yeah, ideally, a recurring issue (eg, "code review on the first monday of the month).
i am now using asana + unito to deal with it.
thanks.
Hey again, just managed with ifttt! Choose a Time and Date, add github account, set correct repository and there you go. Beware: github needed 2 hours to approve the connection to ifttt (you'll get an email when connection is made). You can check if sending failed under "View activity log" in the settings of the applet in ifttt. Cheers. :)
cool! i might try that, thank you!
On Thu, Dec 1, 2016 at 4:23 PM, thomashkov notifications@github.com wrote:
Hey again, just managed with ifttt! Choose a Time and Date, add github account, set correct repository and there you go. Beware: github needed 2 hours to approve the connection to ifttt (you'll get an email when connection is made). You can check if sending failed under "View activity log" in the settings of the applet in ifttt. Cheers. :)
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/isaacs/github/issues/537#issuecomment-264299407, or mute the thread https://github.com/notifications/unsubscribe-auth/AACjco2FCFYQc3F4EBxFSuQzvWzc_0Siks5rDzrYgaJpZM4G7YLn .
-- the glass is all full: half water, half air. neurodata.io, jovo calendar https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York
+1
there are some issues that i have that recur regularly, for example, weekly code review. i currently create a new milestone each week, and each week re-assign the issue to the new week's milestone. this is obviously cumbersome and tedious. i used to use other services (eg, asana, gcal, etc.) for the recurring issues, but i'm on github all day, i don't want a different service for a subset of issues. i imagine other's have recurring issues as well?
does anybody have a better work-around than i do? maybe @zenhubio has some ideas?