Open surchs opened 1 year ago
We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale
label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:
flag:schedule
label to suggest moving this issue into the backlog nowsomeday
label to show that this won't be prioritized. The stalebot will ignore issues with this
label in the future. Use sparingly!We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale
label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:
flag:schedule
label to suggest moving this issue into the backlog nowsomeday
label to show that this won't be prioritized. The stalebot will ignore issues with this
label in the future. Use sparingly!
Our bot PR mover workflow https://github.com/neurobagel/planning/blob/3c1a6e2f6ddc6724dbf8558946f4bc00157ab4ff/.github/workflows/global_move_bot_pr_to_board.yml runs twice a day and then
_bot
label andThis is great unless
The simplest solution would be to check if the PR already has a Status value set, and if so, leave it alone.