Verified Commit 2351a12e authored by anarcat's avatar anarcat
Browse files

fix icebox migration

The second job here would have never ran: the first job would have
repeatedly warned about stale tickets, constantly reseting the timer.

By using the (newly created) ~Stale label, we ensure that

1. the first job doesn't constantly reset the timer (which would have
   been really annoying)

2. that the second job can actually run

This implies reducing the interval on the second job, because it
starts counting after the first one has run.

This also implies that, to reset the *first* timer, the `Stale` label
needs to be removed, which the bot now does as well, if a ~"Needs
Information" ticket gets updated.

(Note that we may want to generalize this to other labels or all
labels, but for now we're keeping the scope limited to ~"Needs
information".)
parent 489eda25
Pipeline #17707 passed with stage
in 49 seconds
......@@ -11,6 +11,8 @@ resource_rules:
state: opened
labels:
- Needs Information
forbidden_labels:
- Stale
limits:
most_recent: 5
actions:
......@@ -19,16 +21,35 @@ resource_rules:
weeks. It needs attention. Please take care of this before
the end of #{14.days.from_now.strftime('%Y-%m-%d')} or it
will be moved to the ~Icebox.
labels:
- Stale
- name: remove stale label on active needs information issues
conditions:
date:
attribute: updated_at
condition: newer_than
interval_type: days
interval: 14
state: opened
labels:
- Needs Information
- Stale
limits:
most_recent: 5
actions:
remove_labels:
- Stale
- name: Freeze ancient needs information issues
conditions:
date:
attribute: updated_at
condition: older_than
interval_type: days
interval: 30
interval: 14
state: opened
labels:
- Needs Information
- Stale
limits:
most_recent: 5
actions:
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment