Issue

[gentlementlegen]

Issue.

[ubiquity-os-development]

# reminder!

[ubiquity-os-development]

# some reminder

[ubiquity-os-development]

# @[object Object], a reminder will be sent in 60000. If no activity is detected, disqualification will occur after 120000. careful!

[ubiquity-os-development]

# @gentlementlegen, a reminder will be sent in 60000.
# If no activity is detected, disqualification will occur after 120000.
# careful!

[gentlementlegen]

Oh yeah I would like to embed it in the starting message but since it is posted by another plugin it is now quite feasible yet. Removing the header.

We can remove the deadline section of the start message for now as well.

[ubiquity-os-development]

Important

• Be sure to link a pull-request before the first reminder to avoid disqualification.
• Reminders will be sent every 2 days 8 hours if there is no activity.
• Assignees will be disqualified after 4 days 16 hours of inactivity.

[ubiquity-os-development]

Important

• Be sure to link a pull-request before the first reminder to avoid disqualification.
• Reminders will be sent every 1 day and 4 hours if there is no activity.
• Assignees will be disqualified after 2 days and 8 hours of inactivity.

[ubiquity-os-development]

Passed the disqualification threshold and no activity is detected, removing assignees: @gentlementlegen.

[ubiquity-os-development]

Important

• Be sure to link a pull-request before the first reminder to avoid disqualification.
• Reminders will be sent every 2 days and 8 hours if there is no activity.
• Assignees will be disqualified after 4 days and 16 hours of inactivity.

[ubiquity-os-development]

Important

• Be sure to link a pull-request before the first reminder to avoid disqualification.
• Reminders will be sent every 1 day and 9 hours if there is no activity.
• Assignees will be disqualified after 2 days and 19 hours of inactivity.