Skip to content

Remove stale bot, replace with "Needs Triage" bot.#1269

Merged
keithamus merged 2 commits intomainfrom
remove-stale-bot
Mar 1, 2026
Merged

Remove stale bot, replace with "Needs Triage" bot.#1269
keithamus merged 2 commits intomainfrom
remove-stale-bot

Conversation

@keithamus
Copy link
Collaborator

It doesn't seem like something we're really embracing. We have a lot of open issues, I think we'd be better off doing some semi-regular triage.

See discussion here, also: https://discord.com/channels/714891843556606052/714891844013785190/1407435550385766571

@gregwhitworth
Copy link
Member

I agree on the regular triage session; ironically the tagging is meant to help with that since it sets the label. Possibly the label itself is sending the wrong message and what we really want is a "needs-triage" style label and no message added unless we can use placeholders (eg: {issue owner} what are the next steps for this issue?). Then we can leverage that label for top pri triaging? That said, a monthly 1 hour triaging session (not the same as the Thursday session) would be useful. Could be open to everyone but chairs are required?

@keithamus
Copy link
Collaborator Author

@gregwhitworth I've added a needs-triage workflow instead. It's essentially the same workflow but with softer wording 😉

@keithamus keithamus changed the title Remove stale bot Remove stale bot, replace with "Needs Triage" bot. Sep 4, 2025
@keithamus keithamus merged commit 6b61bb7 into main Mar 1, 2026
4 of 5 checks passed
@keithamus keithamus deleted the remove-stale-bot branch March 1, 2026 11:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants